0s autopkgtest [05:35:25]: starting date and time: 2025-02-22 05:35:25+0000 0s autopkgtest [05:35:25]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [05:35:25]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.2d6dk8o5/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:glib2.0 --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=glib2.0/2.83.4-1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-ppc64el-15.secgroup --name adt-plucky-ppc64el-libfprint-20250222-053524-juju-7f2275-prod-proposed-migration-environment-15-93f617db-f8bc-41ee-b30b-4f1ac4820118 --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 89s autopkgtest [05:36:54]: testbed dpkg architecture: ppc64el 90s autopkgtest [05:36:55]: testbed apt version: 2.9.30ubuntu1 90s autopkgtest [05:36:55]: @@@@@@@@@@@@@@@@@@@@ test bed setup 90s autopkgtest [05:36:55]: testbed release detected to be: None 91s autopkgtest [05:36:56]: updating testbed package index (apt update) 91s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 92s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 92s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 92s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 92s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 92s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [80.1 kB] 92s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [508 kB] 92s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.5 kB] 92s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [125 kB] 92s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [760 B] 92s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [434 kB] 92s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [3292 B] 92s Fetched 1279 kB in 1s (1156 kB/s) 93s Reading package lists... 94s + lsb_release --codename --short 94s + RELEASE=plucky 94s + cat 94s + [ plucky != trusty ] 94s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y --allow-downgrades -o Dpkg::Options::=--force-confnew dist-upgrade 94s Reading package lists... 94s Building dependency tree... 94s Reading state information... 95s Calculating upgrade... 95s Calculating upgrade... 95s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 95s + rm /etc/apt/preferences.d/force-downgrade-to-release.pref 95s + /usr/lib/apt/apt-helper analyze-pattern ?true 95s + uname -r 95s + sed s/\./\\./g 95s + running_kernel_pattern=^linux-.*6\.12\.0-15-generic.* 95s + apt list ?obsolete 95s + tail -n+2 95s + cut -d/ -f1 95s + grep -v ^linux-.*6\.12\.0-15-generic.* 95s + true 95s + obsolete_pkgs= 95s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y purge --autoremove 95s Reading package lists... 95s Building dependency tree... 95s Reading state information... 96s Solving dependencies... 96s 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 96s + grep -q trusty /etc/lsb-release 96s + [ ! -d /usr/share/doc/unattended-upgrades ] 96s + [ ! -d /usr/share/doc/lxd ] 96s + [ ! -d /usr/share/doc/lxd-client ] 96s + [ ! -d /usr/share/doc/snapd ] 96s + type iptables 96s + cat 96s + chmod 755 /etc/rc.local 96s + . /etc/rc.local 96s + iptables -w -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu 96s + iptables -A OUTPUT -d 10.255.255.1/32 -p tcp -j DROP 96s + iptables -A OUTPUT -d 10.255.255.2/32 -p tcp -j DROP 96s + uname -m 96s + [ ppc64le = ppc64le ] 96s + systemctl is-active keyboard-setup.service 96s + [ active = failed ] 96s + [ -d /run/systemd/system ] 96s + systemd-detect-virt --quiet --vm 96s + mkdir -p /etc/systemd/system/systemd-random-seed.service.d/ 96s + cat 96s + grep -q lz4 /etc/initramfs-tools/initramfs.conf 96s + echo COMPRESS=lz4 96s autopkgtest [05:37:01]: upgrading testbed (apt dist-upgrade and autopurge) 96s Reading package lists... 96s Building dependency tree... 96s Reading state information... 97s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 97s Starting 2 pkgProblemResolver with broken count: 0 97s Done 98s Entering ResolveByKeep 98s 98s Calculating upgrade... 98s The following packages will be upgraded: 98s gir1.2-glib-2.0 libglib2.0-0t64 libglib2.0-data 98s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 98s Need to get 2038 kB of archives. 98s After this operation, 2048 B of additional disk space will be used. 98s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el gir1.2-glib-2.0 ppc64el 2.83.4-1 [184 kB] 98s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libglib2.0-0t64 ppc64el 2.83.4-1 [1801 kB] 99s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el libglib2.0-data all 2.83.4-1 [52.9 kB] 99s Fetched 2038 kB in 1s (2114 kB/s) 100s (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 ... 106371 files and directories currently installed.) 100s Preparing to unpack .../gir1.2-glib-2.0_2.83.4-1_ppc64el.deb ... 100s Unpacking gir1.2-glib-2.0:ppc64el (2.83.4-1) over (2.83.3-2) ... 100s Preparing to unpack .../libglib2.0-0t64_2.83.4-1_ppc64el.deb ... 100s Unpacking libglib2.0-0t64:ppc64el (2.83.4-1) over (2.83.3-2) ... 100s Preparing to unpack .../libglib2.0-data_2.83.4-1_all.deb ... 100s Unpacking libglib2.0-data (2.83.4-1) over (2.83.3-2) ... 100s Setting up libglib2.0-0t64:ppc64el (2.83.4-1) ... 100s No schema files found: doing nothing. 100s Setting up libglib2.0-data (2.83.4-1) ... 100s Setting up gir1.2-glib-2.0:ppc64el (2.83.4-1) ... 100s Processing triggers for libc-bin (2.40-4ubuntu1) ... 100s Reading package lists... 100s Building dependency tree... 100s Reading state information... 100s Starting pkgProblemResolver with broken count: 0 100s Starting 2 pkgProblemResolver with broken count: 0 100s Done 101s Solving dependencies... 101s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 103s autopkgtest [05:37:08]: testbed running kernel: Linux 6.12.0-15-generic #15-Ubuntu SMP Tue Feb 4 16:32:08 UTC 2025 104s autopkgtest [05:37:09]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 111s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (dsc) [2943 B] 111s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (tar) [9291 kB] 111s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (diff) [17.8 kB] 111s gpgv: Signature made Thu Feb 20 18:31:16 2025 UTC 111s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 111s gpgv: Can't check signature: No public key 111s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.9+tod1-1.dsc: no acceptable signature found 112s autopkgtest [05:37:17]: testing package libfprint version 1:1.94.9+tod1-1 113s autopkgtest [05:37:18]: build not needed 115s autopkgtest [05:37:19]: test installed-tests: preparing testbed 115s Reading package lists... 115s Building dependency tree... 115s Reading state information... 115s Starting pkgProblemResolver with broken count: 0 115s Starting 2 pkgProblemResolver with broken count: 0 115s Done 116s The following NEW packages will be installed: 116s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 116s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 116s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libgusb2 116s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 116s python3-cairo umockdev 116s 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded. 116s Need to get 10.0 MB of archives. 116s After this operation, 35.7 MB of additional disk space will be used. 116s Get:1 http://ftpmaster.internal/ubuntu plucky/main ppc64el fonts-dejavu-mono all 2.37-8 [502 kB] 116s Get:2 http://ftpmaster.internal/ubuntu plucky/main ppc64el fonts-dejavu-core all 2.37-8 [835 kB] 117s Get:3 http://ftpmaster.internal/ubuntu plucky/main ppc64el fontconfig-config ppc64el 2.15.0-2ubuntu1 [37.5 kB] 117s Get:4 http://ftpmaster.internal/ubuntu plucky/main ppc64el gir1.2-json-1.0 ppc64el 1.10.6+ds-1 [10.0 kB] 117s Get:5 http://ftpmaster.internal/ubuntu plucky/main ppc64el libgusb2 ppc64el 0.4.9-1 [43.0 kB] 117s Get:6 http://ftpmaster.internal/ubuntu plucky/main ppc64el gir1.2-gusb-1.0 ppc64el 0.4.9-1 [7460 B] 117s Get:7 http://ftpmaster.internal/ubuntu plucky/main ppc64el libpixman-1-0 ppc64el 0.44.0-3 [334 kB] 117s Get:8 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfprint-2-tod1 ppc64el 1:1.94.9+tod1-1 [70.5 kB] 117s Get:9 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfprint-2-2 ppc64el 1:1.94.9+tod1-1 [308 kB] 117s Get:10 http://ftpmaster.internal/ubuntu plucky/main ppc64el gir1.2-fprint-2.0 ppc64el 1:1.94.9+tod1-1 [7236 B] 117s Get:11 http://ftpmaster.internal/ubuntu plucky/universe ppc64el gnome-desktop-testing ppc64el 2021.1-4 [17.7 kB] 117s Get:12 http://ftpmaster.internal/ubuntu plucky/main ppc64el libfontconfig1 ppc64el 2.15.0-2ubuntu1 [188 kB] 117s Get:13 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxcb-render0 ppc64el 1.17.0-2 [17.2 kB] 117s Get:14 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxcb-shm0 ppc64el 1.17.0-2 [5980 B] 117s Get:15 http://ftpmaster.internal/ubuntu plucky/main ppc64el libxrender1 ppc64el 1:0.9.10-1.1build1 [23.1 kB] 117s Get:16 http://ftpmaster.internal/ubuntu plucky/main ppc64el libcairo2 ppc64el 1.18.2-2 [747 kB] 117s Get:17 http://ftpmaster.internal/ubuntu plucky/main ppc64el python3-cairo ppc64el 1.26.1-2build1 [150 kB] 117s Get:18 http://ftpmaster.internal/ubuntu plucky/universe ppc64el libumockdev0 ppc64el 0.19.1-3 [84.6 kB] 117s Get:19 http://ftpmaster.internal/ubuntu plucky/universe ppc64el umockdev ppc64el 0.19.1-3 [84.1 kB] 117s Get:20 http://ftpmaster.internal/ubuntu plucky/universe ppc64el libfprint-2-tests ppc64el 1:1.94.9+tod1-1 [6576 kB] 118s Fetched 10.0 MB in 2s (5766 kB/s) 118s Selecting previously unselected package fonts-dejavu-mono. 118s (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 ... 106371 files and directories currently installed.) 118s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 118s Unpacking fonts-dejavu-mono (2.37-8) ... 118s Selecting previously unselected package fonts-dejavu-core. 118s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 118s Unpacking fonts-dejavu-core (2.37-8) ... 118s Selecting previously unselected package fontconfig-config. 118s Preparing to unpack .../02-fontconfig-config_2.15.0-2ubuntu1_ppc64el.deb ... 118s Unpacking fontconfig-config (2.15.0-2ubuntu1) ... 118s Selecting previously unselected package gir1.2-json-1.0:ppc64el. 118s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_ppc64el.deb ... 118s Unpacking gir1.2-json-1.0:ppc64el (1.10.6+ds-1) ... 118s Selecting previously unselected package libgusb2:ppc64el. 118s Preparing to unpack .../04-libgusb2_0.4.9-1_ppc64el.deb ... 118s Unpacking libgusb2:ppc64el (0.4.9-1) ... 118s Selecting previously unselected package gir1.2-gusb-1.0:ppc64el. 118s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_ppc64el.deb ... 118s Unpacking gir1.2-gusb-1.0:ppc64el (0.4.9-1) ... 118s Selecting previously unselected package libpixman-1-0:ppc64el. 118s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_ppc64el.deb ... 118s Unpacking libpixman-1-0:ppc64el (0.44.0-3) ... 118s Selecting previously unselected package libfprint-2-tod1:ppc64el. 118s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.9+tod1-1_ppc64el.deb ... 118s Unpacking libfprint-2-tod1:ppc64el (1:1.94.9+tod1-1) ... 118s Selecting previously unselected package libfprint-2-2. 118s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.9+tod1-1_ppc64el.deb ... 118s Unpacking libfprint-2-2 (1:1.94.9+tod1-1) ... 118s Selecting previously unselected package gir1.2-fprint-2.0:ppc64el. 118s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.9+tod1-1_ppc64el.deb ... 118s Unpacking gir1.2-fprint-2.0:ppc64el (1:1.94.9+tod1-1) ... 118s Selecting previously unselected package gnome-desktop-testing. 118s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_ppc64el.deb ... 118s Unpacking gnome-desktop-testing (2021.1-4) ... 119s Selecting previously unselected package libfontconfig1:ppc64el. 119s Preparing to unpack .../11-libfontconfig1_2.15.0-2ubuntu1_ppc64el.deb ... 119s Unpacking libfontconfig1:ppc64el (2.15.0-2ubuntu1) ... 119s Selecting previously unselected package libxcb-render0:ppc64el. 119s Preparing to unpack .../12-libxcb-render0_1.17.0-2_ppc64el.deb ... 119s Unpacking libxcb-render0:ppc64el (1.17.0-2) ... 119s Selecting previously unselected package libxcb-shm0:ppc64el. 119s Preparing to unpack .../13-libxcb-shm0_1.17.0-2_ppc64el.deb ... 119s Unpacking libxcb-shm0:ppc64el (1.17.0-2) ... 119s Selecting previously unselected package libxrender1:ppc64el. 119s Preparing to unpack .../14-libxrender1_1%3a0.9.10-1.1build1_ppc64el.deb ... 119s Unpacking libxrender1:ppc64el (1:0.9.10-1.1build1) ... 119s Selecting previously unselected package libcairo2:ppc64el. 119s Preparing to unpack .../15-libcairo2_1.18.2-2_ppc64el.deb ... 119s Unpacking libcairo2:ppc64el (1.18.2-2) ... 119s Selecting previously unselected package python3-cairo. 119s Preparing to unpack .../16-python3-cairo_1.26.1-2build1_ppc64el.deb ... 119s Unpacking python3-cairo (1.26.1-2build1) ... 119s Selecting previously unselected package libumockdev0:ppc64el. 119s Preparing to unpack .../17-libumockdev0_0.19.1-3_ppc64el.deb ... 119s Unpacking libumockdev0:ppc64el (0.19.1-3) ... 119s Selecting previously unselected package umockdev. 119s Preparing to unpack .../18-umockdev_0.19.1-3_ppc64el.deb ... 119s Unpacking umockdev (0.19.1-3) ... 119s Selecting previously unselected package libfprint-2-tests. 119s Preparing to unpack .../19-libfprint-2-tests_1%3a1.94.9+tod1-1_ppc64el.deb ... 119s Unpacking libfprint-2-tests (1:1.94.9+tod1-1) ... 119s Setting up gnome-desktop-testing (2021.1-4) ... 119s Setting up libpixman-1-0:ppc64el (0.44.0-3) ... 119s Setting up libxrender1:ppc64el (1:0.9.10-1.1build1) ... 119s Setting up libxcb-render0:ppc64el (1.17.0-2) ... 119s Setting up libgusb2:ppc64el (0.4.9-1) ... 119s Setting up libfprint-2-tod1:ppc64el (1:1.94.9+tod1-1) ... 119s Setting up libxcb-shm0:ppc64el (1.17.0-2) ... 119s Setting up fonts-dejavu-mono (2.37-8) ... 119s Setting up fonts-dejavu-core (2.37-8) ... 119s Setting up libumockdev0:ppc64el (0.19.1-3) ... 119s Setting up gir1.2-json-1.0:ppc64el (1.10.6+ds-1) ... 119s Setting up libfprint-2-2 (1:1.94.9+tod1-1) ... 129s Setting up umockdev (0.19.1-3) ... 129s Setting up fontconfig-config (2.15.0-2ubuntu1) ... 129s Setting up gir1.2-gusb-1.0:ppc64el (0.4.9-1) ... 129s Setting up libfontconfig1:ppc64el (2.15.0-2ubuntu1) ... 129s Setting up gir1.2-fprint-2.0:ppc64el (1:1.94.9+tod1-1) ... 129s Setting up libcairo2:ppc64el (1.18.2-2) ... 129s Setting up python3-cairo (1.26.1-2build1) ... 130s Setting up libfprint-2-tests (1:1.94.9+tod1-1) ... 130s Processing triggers for man-db (2.13.0-1) ... 130s Processing triggers for udev (257.2-3ubuntu1) ... 131s Processing triggers for libc-bin (2.40-4ubuntu1) ... 132s autopkgtest [05:37:37]: test installed-tests: gnome-desktop-testing-runner libfprint-2 132s autopkgtest [05:37:37]: test installed-tests: [----------------------- 132s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 132s TAP version 14 132s # random seed: R02S62cb195c93c40697e377f4174a4656ca 132s 1..4 132s # Start of context tests 132s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 132s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 132s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x6d8bf8e23590, GType is 9840334891616 132s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 132s ok 1 /context/new 132s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 132s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 132s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 132s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 132s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 132s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 132s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 132s ok 2 /context/no-devices 132s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 132s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 132s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x6d8bf8e23590, GType is 9840334891616 132s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 132s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 132s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 132s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 132s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 132s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 132s # libfprint-context-DEBUG: created 132s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 132s # 132s # libfprint-device-DEBUG: Device reported probe completion 132s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 132s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 132s # 132s # libfprint-device-DEBUG: Device reported open completion 132s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 132s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 132s # 132s # libfprint-device-DEBUG: Device reported close completion 132s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 132s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s ok 3 /context/has-virtual-device 132s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 132s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 132s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x6d8bf8e23590, GType is 9840334891616 132s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 132s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 132s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 132s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 132s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 132s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 132s # libfprint-context-DEBUG: created 132s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 132s # 132s # libfprint-device-DEBUG: Device reported probe completion 132s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 132s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s ok 4 /context/enumerates-new-devices 132s # End of context tests 132s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 132s Running test: libfprint-2/virtual-image.test 132s (process:2892): libfprint-context-DEBUG: 05:37:37.701: Initializing FpContext (libfprint version 1.94.9+tod1) 132s (process:2892): libfprint-tod-DEBUG: 05:37:37.701: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 132s (process:2892): libfprint-context-DEBUG: 05:37:37.705: No driver found for USB device 1D6B:0003 132s (process:2892): libfprint-context-DEBUG: 05:37:37.705: No driver found for USB device 0627:0001 132s (process:2892): libfprint-context-DEBUG: 05:37:37.705: No driver found for USB device 0627:0001 132s (process:2892): libfprint-context-DEBUG: 05:37:37.705: No driver found for USB device 1D6B:0002 132s (process:2892): libfprint-context-DEBUG: 05:37:37.705: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-qia7vx_x/virtual-image.socket 132s (process:2892): libfprint-context-DEBUG: 05:37:37.705: created 132s (process:2892): libfprint-device-DEBUG: 05:37:37.707: Device reported probe completion 132s (process:2892): libfprint-device-DEBUG: 05:37:37.707: Completing action FPI_DEVICE_ACTION_PROBE in idle! 132s (process:2892): libfprint-device-DEBUG: 05:37:37.707: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2892): libfprint-virtual_image-DEBUG: 05:37:37.714: 78553726: ../libfprint/drivers/virtual-image.c:216 132s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:37.714: 78553858: ../libfprint/drivers/virtual-device-listener.c:153 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.814: Image device open completed 132s (process:2892): libfprint-device-DEBUG: 05:37:37.815: Device reported open completion 132s (process:2892): libfprint-device-DEBUG: 05:37:37.815: Completing action FPI_DEVICE_ACTION_OPEN in idle! 132s (process:2892): libfprint-device-DEBUG: 05:37:37.815: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s (process:2892): libfprint-device-DEBUG: 05:37:37.816: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.816: Activating image device 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.816: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.816: Image device activation completed 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.816: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.816: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 132s (process:2892): libfprint-device-DEBUG: 05:37:37.816: Device reported finger status change: FP_FINGER_STATUS_NEEDED 132s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:37.817: Got a new connection! 132s (process:2892): libfprint-device-DEBUG: 05:37:37.817: Idle cancelling on ongoing operation! 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.817: Deactivating image device 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.817: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.817: Image device deactivation completed 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.817: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 132s (process:2892): libfprint-device-DEBUG: 05:37:37.817: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 132s (process:2892): libfprint-device-DEBUG: 05:37:37.817: Device reported capture completion 132s (process:2892): libfprint-device-DEBUG: 05:37:37.817: Device reported finger status change: FP_FINGER_STATUS_NONE 132s (process:2892): libfprint-device-DEBUG: 05:37:37.817: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 132s (process:2892): libfprint-device-DEBUG: 05:37:37.817: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s (process:2892): libfprint-virtual_image-DEBUG: 05:37:37.819: 78658741: ../libfprint/drivers/virtual-image.c:244 132s (process:2892): libfprint-image_device-DEBUG: 05:37:37.919: Image device close completed 132s (process:2892): libfprint-device-DEBUG: 05:37:37.919: Device reported close completion 132s (process:2892): libfprint-device-DEBUG: 05:37:37.919: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 132s (process:2892): libfprint-device-DEBUG: 05:37:37.919: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 132s Capture operation finished 132s Capture cancelled as expected 132s ok 132s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2892): libfprint-virtual_image-DEBUG: 05:37:37.920: 78759807: ../libfprint/drivers/virtual-image.c:216 132s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:37.920: 78759839: ../libfprint/drivers/virtual-device-listener.c:153 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.020: Image device open completed 133s (process:2892): libfprint-device-DEBUG: 05:37:38.020: Device reported open completion 133s (process:2892): libfprint-device-DEBUG: 05:37:38.020: Completing action FPI_DEVICE_ACTION_OPEN in idle! 133s (process:2892): libfprint-device-DEBUG: 05:37:38.020: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 133s (process:2892): libfprint-device-DEBUG: 05:37:38.023: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.023: Activating image device 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.023: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.023: Image device activation completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.023: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.023: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 133s (process:2892): libfprint-device-DEBUG: 05:37:38.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED 133s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:38.023: Got a new connection! 133s (process:2892): libfprint-virtual_image-DEBUG: 05:37:38.024: image data: 0x2de750a0 133s (process:2892): libfprint-device-DEBUG: 05:37:38.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.024: Image device reported finger status: on 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.024: Image device captured an image 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 133s (process:2892): libfprint-device-DEBUG: 05:37:38.024: Device reported finger status change: FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-device-DEBUG: 05:37:38.024: Device reported finger status change: FP_FINGER_STATUS_NONE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.024: Image device reported finger status: off 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image-DEBUG: 05:37:38.072: Minutiae scan completed in 0.047871 secs 133s (process:2892): libfprint-device-DEBUG: 05:37:38.073: Device reported enroll progress, reported 1 of 5 have been completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.073: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 133s (process:2892): libfprint-device-DEBUG: 05:37:38.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED 133s (process:2892): libfprint-device-DEBUG: 05:37:38.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.073: Image device reported finger status: on 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.073: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 133s (process:2892): libfprint-virtual_image-DEBUG: 05:37:38.074: image data: 0x2de65890 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.074: Image device captured an image 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.074: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 133s (process:2892): libfprint-device-DEBUG: 05:37:38.074: Device reported finger status change: FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image-DEBUG: 05:37:38.111: Minutiae scan completed in 0.037382 secs 133s (process:2892): libfprint-device-DEBUG: 05:37:38.112: Device reported enroll progress, reported 2 of 5 have been completed 133s (process:2892): libfprint-device-DEBUG: 05:37:38.112: Device reported finger status change: FP_FINGER_STATUS_NONE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.112: Image device reported finger status: off 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.112: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.112: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 133s (process:2892): libfprint-device-DEBUG: 05:37:38.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 133s (process:2892): libfprint-virtual_image-DEBUG: 05:37:38.113: image data: 0x2de65890 133s (process:2892): libfprint-device-DEBUG: 05:37:38.113: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.113: Image device reported finger status: on 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.113: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.113: Image device captured an image 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.113: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 133s (process:2892): libfprint-device-DEBUG: 05:37:38.113: Device reported finger status change: FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-device-DEBUG: 05:37:38.113: Device reported finger status change: FP_FINGER_STATUS_NONE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.113: Image device reported finger status: off 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.113: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image-DEBUG: 05:37:38.149: Minutiae scan completed in 0.036160 secs 133s (process:2892): libfprint-device-DEBUG: 05:37:38.150: Device reported enroll progress, reported 3 of 5 have been completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.150: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 133s (process:2892): libfprint-device-DEBUG: 05:37:38.150: Device reported finger status change: FP_FINGER_STATUS_NEEDED 133s (process:2892): libfprint-virtual_image-DEBUG: 05:37:38.150: image data: 0x2de65890 133s (process:2892): libfprint-device-DEBUG: 05:37:38.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.151: Image device reported finger status: on 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.151: Image device captured an image 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 133s (process:2892): libfprint-device-DEBUG: 05:37:38.151: Device reported finger status change: FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-device-DEBUG: 05:37:38.151: Device reported finger status change: FP_FINGER_STATUS_NONE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.151: Image device reported finger status: off 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.151: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-device-DEBUG: 05:37:38.157: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 133s (process:2892): libfprint-image-DEBUG: 05:37:38.192: Minutiae scan completed in 0.040951 secs 133s (process:2892): libfprint-device-DEBUG: 05:37:38.192: Device reported enroll progress, reported 4 of 5 have been completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 133s (process:2892): libfprint-device-DEBUG: 05:37:38.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 133s (process:2892): libfprint-virtual_image-DEBUG: 05:37:38.193: image data: 0x2de65890 133s (process:2892): libfprint-device-DEBUG: 05:37:38.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.193: Image device reported finger status: on 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.193: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.193: Image device captured an image 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.193: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 133s (process:2892): libfprint-device-DEBUG: 05:37:38.193: Device reported finger status change: FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-device-DEBUG: 05:37:38.193: Device reported finger status change: FP_FINGER_STATUS_NONE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.193: Image device reported finger status: off 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.193: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image-DEBUG: 05:37:38.229: Minutiae scan completed in 0.035681 secs 133s (process:2892): libfprint-device-DEBUG: 05:37:38.229: Device reported enroll progress, reported 5 of 5 have been completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.230: Deactivating image device 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.230: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.230: Image device deactivation completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.230: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 133s (process:2892): libfprint-device-DEBUG: 05:37:38.230: Device reported enroll completion 133s (process:2892): libfprint-device-DEBUG: 05:37:38.230: Print for finger FP_FINGER_LEFT_THUMB enrolled 133s (process:2892): libfprint-device-DEBUG: 05:37:38.230: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 133s (process:2892): libfprint-device-DEBUG: 05:37:38.230: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 133s (process:2892): libfprint-device-DEBUG: 05:37:38.231: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Activating image device 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device activation completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 133s (process:2892): libfprint-device-DEBUG: 05:37:38.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 133s (process:2892): libfprint-virtual_image-DEBUG: 05:37:38.231: image data: 0x2de65890 133s (process:2892): libfprint-device-DEBUG: 05:37:38.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device reported finger status: on 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device captured an image 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 133s (process:2892): libfprint-device-DEBUG: 05:37:38.231: Device reported finger status change: FP_FINGER_STATUS_PRESENT 133s (process:2892): libfprint-device-DEBUG: 05:37:38.231: Device reported finger status change: FP_FINGER_STATUS_NONE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.231: Image device reported finger status: off 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.232: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.232: Deactivating image device 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.232: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.232: Image device deactivation completed 133s (process:2892): libfprint-image_device-DEBUG: 05:37:38.232: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 133s (process:2892): libfprint-image-DEBUG: 05:37:38.272: Minutiae scan completed in 0.040467 secs 134s (process:2892): libfprint-print-DEBUG: 05:37:39.515: score 1093/40 134s (process:2892): libfprint-device-DEBUG: 05:37:39.515: Device reported verify result 134s (process:2892): libfprint-device-DEBUG: 05:37:39.515: Device reported verify completion 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Updated temperature model after 1.28 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Activating image device 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device activation completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.516: image data: 0x2dec7b40 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-device-DEBUG: 05:37:39.516: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Deactivating image device 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device deactivation completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 134s (process:2892): libfprint-image-DEBUG: 05:37:39.544: Minutiae scan completed in 0.027417 secs 134s (process:2892): libfprint-print-DEBUG: 05:37:39.553: score 10/40 134s (process:2892): libfprint-print-DEBUG: 05:37:39.560: score 10/40 134s (process:2892): libfprint-print-DEBUG: 05:37:39.568: score 10/40 134s (process:2892): libfprint-print-DEBUG: 05:37:39.576: score 10/40 134s (process:2892): libfprint-print-DEBUG: 05:37:39.585: score 10/40 134s (process:2892): libfprint-device-DEBUG: 05:37:39.585: Device reported verify result 134s (process:2892): libfprint-device-DEBUG: 05:37:39.585: Device reported verify completion 134s (process:2892): libfprint-device-DEBUG: 05:37:39.585: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 134s (process:2892): libfprint-device-DEBUG: 05:37:39.585: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s (process:2892): libfprint-device-DEBUG: 05:37:39.585: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.585: Activating image device 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.585: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device activation completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.586: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.586: image data: 0x2ded6b50 134s (process:2892): libfprint-device-DEBUG: 05:37:39.586: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.586: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-device-DEBUG: 05:37:39.586: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.586: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image-DEBUG: 05:37:39.612: Minutiae scan completed in 0.025891 secs 134s (process:2892): libfprint-device-DEBUG: 05:37:39.612: Device reported enroll progress, reported 1 of 5 have been completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.612: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.612: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-device-DEBUG: 05:37:39.613: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.613: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.613: image data: 0x2ded6b50 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.613: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.613: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.613: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image-DEBUG: 05:37:39.639: Minutiae scan completed in 0.025812 secs 134s (process:2892): libfprint-device-DEBUG: 05:37:39.639: Device reported enroll progress, reported 2 of 5 have been completed 134s (process:2892): libfprint-device-DEBUG: 05:37:39.639: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.639: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.639: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.639: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.640: image data: 0x2ded6b50 134s (process:2892): libfprint-device-DEBUG: 05:37:39.640: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.640: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.640: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.640: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.640: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.640: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-device-DEBUG: 05:37:39.640: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.640: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.640: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image-DEBUG: 05:37:39.665: Minutiae scan completed in 0.024969 secs 134s (process:2892): libfprint-device-DEBUG: 05:37:39.665: Device reported enroll progress, reported 3 of 5 have been completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.665: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.665: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.666: image data: 0x2ded6b50 134s (process:2892): libfprint-device-DEBUG: 05:37:39.666: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.666: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.666: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.666: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.666: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.666: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-device-DEBUG: 05:37:39.666: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.666: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.666: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image-DEBUG: 05:37:39.692: Minutiae scan completed in 0.025728 secs 134s (process:2892): libfprint-device-DEBUG: 05:37:39.692: Device reported enroll progress, reported 4 of 5 have been completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.692: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.692: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.692: image data: 0x2ded6b50 134s (process:2892): libfprint-device-DEBUG: 05:37:39.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.693: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.693: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.693: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.693: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.693: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-device-DEBUG: 05:37:39.693: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.693: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.693: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image-DEBUG: 05:37:39.720: Minutiae scan completed in 0.026974 secs 134s (process:2892): libfprint-device-DEBUG: 05:37:39.720: Device reported enroll progress, reported 5 of 5 have been completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.720: Deactivating image device 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.720: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.720: Image device deactivation completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.720: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 134s (process:2892): libfprint-device-DEBUG: 05:37:39.720: Device reported enroll completion 134s (process:2892): libfprint-device-DEBUG: 05:37:39.720: Print for finger FP_FINGER_LEFT_THUMB enrolled 134s (process:2892): libfprint-device-DEBUG: 05:37:39.720: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 134s (process:2892): libfprint-device-DEBUG: 05:37:39.720: Updated temperature model after 0.14 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s (process:2892): libfprint-device-DEBUG: 05:37:39.721: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Activating image device 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device activation completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 134s (process:2892): libfprint-device-DEBUG: 05:37:39.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 134s (process:2892): libfprint-virtual_image-DEBUG: 05:37:39.721: image data: 0x2deb8b00 134s (process:2892): libfprint-device-DEBUG: 05:37:39.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device reported finger status: on 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device captured an image 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 134s (process:2892): libfprint-device-DEBUG: 05:37:39.721: Device reported finger status change: FP_FINGER_STATUS_PRESENT 134s (process:2892): libfprint-device-DEBUG: 05:37:39.721: Device reported finger status change: FP_FINGER_STATUS_NONE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device reported finger status: off 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Deactivating image device 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device deactivation completed 134s (process:2892): libfprint-image_device-DEBUG: 05:37:39.721: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 134s (process:2892): libfprint-image-DEBUG: 05:37:39.753: Minutiae scan completed in 0.030813 secs 135s (process:2892): libfprint-print-DEBUG: 05:37:40.916: score 1093/40 135s (process:2892): libfprint-device-DEBUG: 05:37:40.916: Device reported verify result 135s (process:2892): libfprint-device-DEBUG: 05:37:40.916: Device reported verify completion 135s (process:2892): libfprint-device-DEBUG: 05:37:40.918: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s (process:2892): libfprint-device-DEBUG: 05:37:40.918: Updated temperature model after 1.20 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:2892): libfprint-device-DEBUG: 05:37:40.918: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.918: Activating image device 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.918: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.918: Image device activation completed 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.918: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.918: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 135s (process:2892): libfprint-device-DEBUG: 05:37:40.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:2892): libfprint-virtual_image-DEBUG: 05:37:40.919: image data: 0x2dec7b40 135s (process:2892): libfprint-device-DEBUG: 05:37:40.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.920: Image device reported finger status: on 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.920: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.920: Image device captured an image 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 135s (process:2892): libfprint-device-DEBUG: 05:37:40.924: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:2892): libfprint-device-DEBUG: 05:37:40.924: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Image device reported finger status: off 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Deactivating image device 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Image device deactivation completed 135s (process:2892): libfprint-image_device-DEBUG: 05:37:40.924: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 136s (process:2892): libfprint-image-DEBUG: 05:37:40.944: Minutiae scan completed in 0.024355 secs 136s (process:2892): libfprint-print-DEBUG: 05:37:40.953: score 10/40 136s (process:2892): libfprint-print-DEBUG: 05:37:40.960: score 10/40 136s (process:2892): libfprint-print-DEBUG: 05:37:40.966: score 10/40 136s (process:2892): libfprint-print-DEBUG: 05:37:40.973: score 10/40 136s (process:2892): libfprint-print-DEBUG: 05:37:40.980: score 10/40 136s (process:2892): libfprint-print-DEBUG: 05:37:41.203: score 855/40 136s (process:2892): libfprint-device-DEBUG: 05:37:41.203: Device reported verify result 136s (process:2892): libfprint-device-DEBUG: 05:37:41.203: Device reported verify completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Updated temperature model after 0.29 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Activating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device activation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Device reported verify result 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Deactivating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device deactivation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Device reported verify completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.204: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Activating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device activation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Deactivating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device deactivation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.205: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Device reported verify completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.205: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.205: 82044934: ../libfprint/drivers/virtual-image.c:244 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.305: Image device close completed 136s (process:2892): libfprint-device-DEBUG: 05:37:41.305: Device reported close completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.305: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.305: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s Print was processed, continuing 136s Print was processed, continuing 136s Print was processed, continuing 136s Print was processed, continuing 136s Print was processed, continuing 136s Enroll done 136s Print was processed, continuing 136s Print was processed, continuing 136s Print was processed, continuing 136s Print was processed, continuing 136s Print was processed, continuing 136s Enroll done 136s fp - device - error - quark: An unspecified error occurred! (0) 136s ok 136s test_features (__main__.VirtualImage.test_features) ... (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.306: 82145706: ../libfprint/drivers/virtual-image.c:216 136s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:41.306: 82145734: ../libfprint/drivers/virtual-device-listener.c:153 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.406: Image device open completed 136s (process:2892): libfprint-device-DEBUG: 05:37:41.406: Device reported open completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.406: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.406: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.406: 82245991: ../libfprint/drivers/virtual-image.c:244 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.506: Image device close completed 136s (process:2892): libfprint-device-DEBUG: 05:37:41.506: Device reported close completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.506: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.506: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 136s test_identify (__main__.VirtualImage.test_identify) ... (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.506: 82346441: ../libfprint/drivers/virtual-image.c:216 136s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:41.506: 82346461: ../libfprint/drivers/virtual-device-listener.c:153 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.606: Image device open completed 136s (process:2892): libfprint-device-DEBUG: 05:37:41.606: Device reported open completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.606: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.606: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-device-DEBUG: 05:37:41.607: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Activating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device activation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:41.607: Got a new connection! 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.607: image data: 0x2deb8b00 136s (process:2892): libfprint-device-DEBUG: 05:37:41.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.607: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.608: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.608: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.608: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.608: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.608: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.636: Minutiae scan completed in 0.028244 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.636: Device reported enroll progress, reported 1 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.637: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.637: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-device-DEBUG: 05:37:41.637: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.637: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.637: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.637: image data: 0x2deb8b00 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.637: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.637: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.637: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image-DEBUG: 05:37:41.666: Minutiae scan completed in 0.029142 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.667: Device reported enroll progress, reported 2 of 5 have been completed 136s (process:2892): libfprint-device-DEBUG: 05:37:41.667: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.667: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.667: image data: 0x2deb8b00 136s (process:2892): libfprint-device-DEBUG: 05:37:41.667: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.667: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.667: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.667: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.695: Minutiae scan completed in 0.027894 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.696: Device reported enroll progress, reported 3 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.696: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.696: image data: 0x2deb8b00 136s (process:2892): libfprint-device-DEBUG: 05:37:41.696: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.696: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.696: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.696: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.724: Minutiae scan completed in 0.027983 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.725: Device reported enroll progress, reported 4 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.725: image data: 0x2deb8b00 136s (process:2892): libfprint-device-DEBUG: 05:37:41.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.725: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.725: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.754: Minutiae scan completed in 0.029203 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.755: Device reported enroll progress, reported 5 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.755: Deactivating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.755: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.755: Image device deactivation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.755: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 136s (process:2892): libfprint-device-DEBUG: 05:37:41.755: Device reported enroll completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.755: Print for finger FP_FINGER_LEFT_THUMB enrolled 136s (process:2892): libfprint-device-DEBUG: 05:37:41.755: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.755: Updated temperature model after 0.15 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-device-DEBUG: 05:37:41.756: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Activating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device activation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.756: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.756: image data: 0x2ded6b70 136s (process:2892): libfprint-device-DEBUG: 05:37:41.756: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.756: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.756: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.785: Minutiae scan completed in 0.028819 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.785: Device reported enroll progress, reported 1 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.785: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-device-DEBUG: 05:37:41.786: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.786: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.786: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.786: image data: 0x2ded6b70 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.786: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.786: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.786: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image-DEBUG: 05:37:41.817: Minutiae scan completed in 0.030934 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.817: Device reported enroll progress, reported 2 of 5 have been completed 136s (process:2892): libfprint-device-DEBUG: 05:37:41.818: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.818: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.818: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.818: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.818: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.818: image data: 0x2ded6b70 136s (process:2892): libfprint-device-DEBUG: 05:37:41.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.819: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.819: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.819: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.819: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.819: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.819: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.819: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.819: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.845: Minutiae scan completed in 0.026019 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.845: Device reported enroll progress, reported 3 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.846: image data: 0x2ded6b70 136s (process:2892): libfprint-device-DEBUG: 05:37:41.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.846: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.846: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.846: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.846: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.846: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.874: Minutiae scan completed in 0.028619 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.875: Device reported enroll progress, reported 4 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.875: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.875: image data: 0x2ded6b70 136s (process:2892): libfprint-device-DEBUG: 05:37:41.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.875: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.875: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.875: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.875: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.876: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.876: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.876: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.876: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.905: Minutiae scan completed in 0.029650 secs 136s (process:2892): libfprint-device-DEBUG: 05:37:41.905: Device reported enroll progress, reported 5 of 5 have been completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Deactivating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device deactivation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 136s (process:2892): libfprint-device-DEBUG: 05:37:41.906: Device reported enroll completion 136s (process:2892): libfprint-device-DEBUG: 05:37:41.906: Print for finger FP_FINGER_LEFT_THUMB enrolled 136s (process:2892): libfprint-device-DEBUG: 05:37:41.906: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s (process:2892): libfprint-device-DEBUG: 05:37:41.906: Updated temperature model after 0.15 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-device-DEBUG: 05:37:41.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Activating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device activation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 136s (process:2892): libfprint-device-DEBUG: 05:37:41.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s (process:2892): libfprint-virtual_image-DEBUG: 05:37:41.906: image data: 0x2ded6b70 136s (process:2892): libfprint-device-DEBUG: 05:37:41.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device reported finger status: on 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device captured an image 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 136s (process:2892): libfprint-device-DEBUG: 05:37:41.907: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s (process:2892): libfprint-device-DEBUG: 05:37:41.907: Device reported finger status change: FP_FINGER_STATUS_NONE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device reported finger status: off 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Deactivating image device 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device deactivation completed 136s (process:2892): libfprint-image_device-DEBUG: 05:37:41.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 136s (process:2892): libfprint-image-DEBUG: 05:37:41.938: Minutiae scan completed in 0.031768 secs 136s (process:2892): libfprint-print-DEBUG: 05:37:41.951: score 10/40 136s (process:2892): libfprint-print-DEBUG: 05:37:41.965: score 10/40 137s (process:2892): libfprint-print-DEBUG: 05:37:41.977: score 10/40 137s (process:2892): libfprint-print-DEBUG: 05:37:41.986: score 10/40 137s (process:2892): libfprint-print-DEBUG: 05:37:41.995: score 10/40 137s (process:2892): libfprint-print-DEBUG: 05:37:42.297: score 855/40 137s (process:2892): libfprint-device-DEBUG: 05:37:42.297: Device reported identify result 137s (process:2892): libfprint-device-DEBUG: 05:37:42.298: Device reported identify completion 137s (process:2892): libfprint-device-DEBUG: 05:37:42.298: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 137s (process:2892): libfprint-device-DEBUG: 05:37:42.298: Updated temperature model after 0.39 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 137s (process:2892): libfprint-device-DEBUG: 05:37:42.299: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Activating image device 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device activation completed 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 137s (process:2892): libfprint-device-DEBUG: 05:37:42.299: Device reported finger status change: FP_FINGER_STATUS_NEEDED 137s (process:2892): libfprint-virtual_image-DEBUG: 05:37:42.299: image data: 0x2deb8b00 137s (process:2892): libfprint-device-DEBUG: 05:37:42.299: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device reported finger status: on 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device captured an image 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.299: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 137s (process:2892): libfprint-device-DEBUG: 05:37:42.304: Device reported finger status change: FP_FINGER_STATUS_PRESENT 137s (process:2892): libfprint-device-DEBUG: 05:37:42.304: Device reported finger status change: FP_FINGER_STATUS_NONE 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.304: Image device reported finger status: off 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.304: Deactivating image device 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.304: Image device deactivation completed 137s (process:2892): libfprint-image_device-DEBUG: 05:37:42.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 137s (process:2892): libfprint-image-DEBUG: 05:37:42.333: Minutiae scan completed in 0.033673 secs 138s Executing: libfprint-2/virtual-image.test 138s (process:2892): libfprint-print-DEBUG: 05:37:43.690: score 1093/40 138s (process:2892): libfprint-device-DEBUG: 05:37:43.690: Device reported identify result 138s (process:2892): libfprint-device-DEBUG: 05:37:43.690: Device reported identify completion 138s (process:2892): libfprint-device-DEBUG: 05:37:43.690: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 138s (process:2892): libfprint-device-DEBUG: 05:37:43.690: Updated temperature model after 1.39 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Activating image device 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device activation completed 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Device reported identify result 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Deactivating image device 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device deactivation completed 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Device reported identify completion 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Device reported finger status change: FP_FINGER_STATUS_NONE 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Activating image device 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device activation completed 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 138s (process:2892): libfprint-device-DEBUG: 05:37:43.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.691: Deactivating image device 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.692: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.692: Image device deactivation completed 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.692: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 138s (process:2892): libfprint-device-DEBUG: 05:37:43.692: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 138s (process:2892): libfprint-device-DEBUG: 05:37:43.692: Device reported identify completion 138s (process:2892): libfprint-device-DEBUG: 05:37:43.692: Device reported finger status change: FP_FINGER_STATUS_NONE 138s (process:2892): libfprint-device-DEBUG: 05:37:43.692: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 138s (process:2892): libfprint-device-DEBUG: 05:37:43.692: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-virtual_image-DEBUG: 05:37:43.692: 84531845: ../libfprint/drivers/virtual-image.c:244 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.792: Image device close completed 138s (process:2892): libfprint-device-DEBUG: 05:37:43.792: Device reported close completion 138s (process:2892): libfprint-device-DEBUG: 05:37:43.792: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 138s (process:2892): libfprint-device-DEBUG: 05:37:43.792: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s Print was processed, continuing 138s Print was processed, continuing 138s Print was processed, continuing 138s Print was processed, continuing 138s Print was processed, continuing 138s Enroll done 138s Print was processed, continuing 138s Print was processed, continuing 138s Print was processed, continuing 138s Print was processed, continuing 138s Print was processed, continuing 138s Enroll done 138s Identify finished 138s Identify finished 138s Identify finished 138s fp - device - retry - quark: The swipe was too short, please try again. (1) 138s Identify finished 138s fp - device - error - quark: An unspecified error occurred! (0) 138s ok 138s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2892): libfprint-virtual_image-DEBUG: 05:37:43.793: 84632905: ../libfprint/drivers/virtual-image.c:216 138s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:43.793: 84632948: ../libfprint/drivers/virtual-device-listener.c:153 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.893: Image device open completed 138s (process:2892): libfprint-device-DEBUG: 05:37:43.893: Device reported open completion 138s (process:2892): libfprint-device-DEBUG: 05:37:43.893: Completing action FPI_DEVICE_ACTION_OPEN in idle! 138s (process:2892): libfprint-device-DEBUG: 05:37:43.893: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-device-DEBUG: 05:37:43.894: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Activating image device 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device activation completed 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 138s (process:2892): libfprint-device-DEBUG: 05:37:43.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 138s (process:2892): libfprint-virtual_device_connection-DEBUG: 05:37:43.894: Got a new connection! 138s (process:2892): libfprint-virtual_image-DEBUG: 05:37:43.894: image data: 0x2dec7390 138s (process:2892): libfprint-device-DEBUG: 05:37:43.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device reported finger status: on 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device captured an image 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 138s (process:2892): libfprint-device-DEBUG: 05:37:43.894: Device reported finger status change: FP_FINGER_STATUS_PRESENT 138s (process:2892): libfprint-device-DEBUG: 05:37:43.894: Device reported finger status change: FP_FINGER_STATUS_NONE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device reported finger status: off 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 138s (process:2892): libfprint-image-DEBUG: 05:37:43.927: Minutiae scan completed in 0.032491 secs 138s (process:2892): libfprint-device-DEBUG: 05:37:43.927: Device reported enroll progress, reported 1 of 5 have been completed 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.928: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 138s (process:2892): libfprint-device-DEBUG: 05:37:43.928: Device reported finger status change: FP_FINGER_STATUS_NEEDED 138s (process:2892): libfprint-device-DEBUG: 05:37:43.928: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.928: Image device reported finger status: on 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.928: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 138s (process:2892): libfprint-virtual_image-DEBUG: 05:37:43.929: image data: 0x2dec7390 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.929: Image device captured an image 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.929: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 138s (process:2892): libfprint-device-DEBUG: 05:37:43.929: Device reported finger status change: FP_FINGER_STATUS_PRESENT 138s (process:2892): libfprint-image-DEBUG: 05:37:43.964: Minutiae scan completed in 0.035232 secs 138s (process:2892): libfprint-device-DEBUG: 05:37:43.965: Device reported enroll progress, reported 2 of 5 have been completed 138s (process:2892): libfprint-device-DEBUG: 05:37:43.965: Device reported finger status change: FP_FINGER_STATUS_NONE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.965: Image device reported finger status: off 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 138s (process:2892): libfprint-device-DEBUG: 05:37:43.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 138s (process:2892): libfprint-virtual_image-DEBUG: 05:37:43.965: image data: 0x2dec7390 138s (process:2892): libfprint-device-DEBUG: 05:37:43.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.965: Image device reported finger status: on 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.965: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.966: Image device captured an image 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 138s (process:2892): libfprint-device-DEBUG: 05:37:43.966: Device reported finger status change: FP_FINGER_STATUS_PRESENT 138s (process:2892): libfprint-device-DEBUG: 05:37:43.966: Device reported finger status change: FP_FINGER_STATUS_NONE 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.966: Image device reported finger status: off 138s (process:2892): libfprint-image_device-DEBUG: 05:37:43.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:2892): libfprint-image-DEBUG: 05:37:43.999: Minutiae scan completed in 0.033230 secs 139s (process:2892): libfprint-device-DEBUG: 05:37:43.999: Device reported enroll progress, reported 3 of 5 have been completed 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 139s (process:2892): libfprint-device-DEBUG: 05:37:44.000: Device reported finger status change: FP_FINGER_STATUS_NEEDED 139s (process:2892): libfprint-virtual_image-DEBUG: 05:37:44.000: image data: 0x2dec7390 139s (process:2892): libfprint-device-DEBUG: 05:37:44.000: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.000: Image device reported finger status: on 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.000: Image device captured an image 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 139s (process:2892): libfprint-device-DEBUG: 05:37:44.000: Device reported finger status change: FP_FINGER_STATUS_PRESENT 139s (process:2892): libfprint-device-DEBUG: 05:37:44.001: Device reported finger status change: FP_FINGER_STATUS_NONE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.001: Image device reported finger status: off 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.001: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:2892): libfprint-image-DEBUG: 05:37:44.033: Minutiae scan completed in 0.032210 secs 139s (process:2892): libfprint-device-DEBUG: 05:37:44.033: Device reported enroll progress, reported 4 of 5 have been completed 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 139s (process:2892): libfprint-device-DEBUG: 05:37:44.033: Device reported finger status change: FP_FINGER_STATUS_NEEDED 139s (process:2892): libfprint-virtual_image-DEBUG: 05:37:44.034: image data: 0x2dec7390 139s (process:2892): libfprint-device-DEBUG: 05:37:44.034: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.034: Image device reported finger status: on 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.034: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.034: Image device captured an image 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.034: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 139s (process:2892): libfprint-device-DEBUG: 05:37:44.034: Device reported finger status change: FP_FINGER_STATUS_PRESENT 139s (process:2892): libfprint-device-DEBUG: 05:37:44.034: Device reported finger status change: FP_FINGER_STATUS_NONE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.034: Image device reported finger status: off 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.034: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:2892): libfprint-image-DEBUG: 05:37:44.071: Minutiae scan completed in 0.037534 secs 139s (process:2892): libfprint-device-DEBUG: 05:37:44.072: Device reported enroll progress, reported 5 of 5 have been completed 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.072: Deactivating image device 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.072: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.072: Image device deactivation completed 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.072: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 139s (process:2892): libfprint-device-DEBUG: 05:37:44.072: Device reported enroll completion 139s (process:2892): libfprint-device-DEBUG: 05:37:44.072: Print for finger FP_FINGER_LEFT_THUMB enrolled 139s (process:2892): libfprint-device-DEBUG: 05:37:44.072: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 139s (process:2892): libfprint-device-DEBUG: 05:37:44.072: Updated temperature model after 0.18 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 139s (process:2892): libfprint-device-DEBUG: 05:37:44.073: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.073: Activating image device 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.073: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.073: Image device activation completed 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.073: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.073: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 139s (process:2892): libfprint-device-DEBUG: 05:37:44.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED 139s (process:2892): libfprint-virtual_image-DEBUG: 05:37:44.073: image data: 0x2dec7390 139s (process:2892): libfprint-device-DEBUG: 05:37:44.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.074: Image device reported finger status: on 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.074: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.074: Image device captured an image 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.074: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 139s (process:2892): libfprint-device-DEBUG: 05:37:44.076: Device reported finger status change: FP_FINGER_STATUS_PRESENT 139s (process:2892): libfprint-device-DEBUG: 05:37:44.076: Device reported finger status change: FP_FINGER_STATUS_NONE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.076: Image device reported finger status: off 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.076: Deactivating image device 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.076: Image device deactivation completed 139s (process:2892): libfprint-image_device-DEBUG: 05:37:44.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 139s (process:2892): libfprint-image-DEBUG: 05:37:44.108: Minutiae scan completed in 0.034270 secs 140s (process:2892): libfprint-print-DEBUG: 05:37:45.474: score 1093/40 140s (process:2892): libfprint-device-DEBUG: 05:37:45.474: Device reported verify result 140s (process:2892): libfprint-device-DEBUG: 05:37:45.474: Device reported verify completion 140s (process:2892): libfprint-device-DEBUG: 05:37:45.474: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 140s (process:2892): libfprint-device-DEBUG: 05:37:45.475: Updated temperature model after 1.40 seconds, ratio 0.29 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 140s (process:2892): libfprint-device-DEBUG: 05:37:45.475: Updated temperature model after 0.00 seconds, ratio 0.30 -> 0.30, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Activating image device 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device activation completed 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 140s (process:2892): libfprint-device-DEBUG: 05:37:45.475: Device reported finger status change: FP_FINGER_STATUS_NEEDED 140s (process:2892): libfprint-virtual_image-DEBUG: 05:37:45.475: image data: 0x2ded6b70 140s (process:2892): libfprint-device-DEBUG: 05:37:45.475: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device reported finger status: on 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.475: Image device captured an image 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 140s (process:2892): libfprint-device-DEBUG: 05:37:45.480: Device reported finger status change: FP_FINGER_STATUS_PRESENT 140s (process:2892): libfprint-device-DEBUG: 05:37:45.480: Device reported finger status change: FP_FINGER_STATUS_NONE 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Image device reported finger status: off 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Deactivating image device 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Image device deactivation completed 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.480: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 140s (process:2892): libfprint-image-DEBUG: 05:37:45.506: Minutiae scan completed in 0.030301 secs 140s (process:2892): libfprint-print-DEBUG: 05:37:45.514: score 10/40 140s (process:2892): libfprint-print-DEBUG: 05:37:45.521: score 10/40 140s (process:2892): libfprint-print-DEBUG: 05:37:45.528: score 10/40 140s (process:2892): libfprint-print-DEBUG: 05:37:45.535: score 10/40 140s (process:2892): libfprint-print-DEBUG: 05:37:45.542: score 10/40 140s (process:2892): libfprint-device-DEBUG: 05:37:45.542: Device reported verify result 140s (process:2892): libfprint-device-DEBUG: 05:37:45.542: Device reported verify completion 140s (process:2892): libfprint-device-DEBUG: 05:37:45.542: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 140s (process:2892): libfprint-device-DEBUG: 05:37:45.542: Updated temperature model after 0.07 seconds, ratio 0.30 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 140s (process:2892): libfprint-virtual_image-DEBUG: 05:37:45.542: 86381993: ../libfprint/drivers/virtual-image.c:244 140s (process:2892): libfprint-image_device-DEBUG: 05:37:45.642: Image device close completed 140s (process:2892): libfprint-device-DEBUG: 05:37:45.642: Device reported close completion 140s (process:2892): libfprint-device-DEBUG: 05:37:45.642: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 140s (process:2892): libfprint-device-DEBUG: 05:37:45.642: Updated temperature model after 0.10 seconds, ratio 0.30 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 140s Print was processed, continuing 140s Print was processed, continuing 140s Print was processed, continuing 140s Print was processed, continuing 140s Print was processed, continuing 140s Enroll done 140s ok 140s 140s ---------------------------------------------------------------------- 140s Ran 5 tests in 7.944s 140s 140s OK 140s PASS: libfprint-2/virtual-image.test 140s Running test: libfprint-2/driver-vfs301.test 140s ** (umockdev-run:2901): DEBUG: 05:37:45.729: umockdev.vala:127: Created udev test bed /tmp/umockdev.4O6212 140s ** (umockdev-run:2901): DEBUG: 05:37:45.729: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 140s ** (umockdev-run:2901): DEBUG: 05:37:45.731: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 140s ** (umockdev-run:2901): DEBUG: 05:37:45.734: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4O6212/dev/bus/usb/002/005 140s ** (umockdev-run:2901): DEBUG: 05:37:45.734: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 140s ** (umockdev-run:2901): DEBUG: 05:37:45.736: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 140s ** (umockdev-run:2901): DEBUG: 05:37:45.740: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4O6212/dev/bus/usb/002/002 140s ** (umockdev-run:2901): DEBUG: 05:37:45.740: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 140s ** (umockdev-run:2901): DEBUG: 05:37:45.741: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 140s ** (umockdev-run:2901): DEBUG: 05:37:45.748: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4O6212/dev/bus/usb/002/001 140s ** (umockdev-run:2901): DEBUG: 05:37:45.748: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0 140s ** (umockdev-run:2901): DEBUG: 05:37:45.748: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 140s (umockdev-run:2901): GLib-GIO-DEBUG: 05:37:45.752: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 140s (process:2905): libfprint-context-DEBUG: 05:37:45.884: Initializing FpContext (libfprint version 1.94.9+tod1) 140s (process:2905): libfprint-tod-DEBUG: 05:37:45.885: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 140s (process:2905): libfprint-context-DEBUG: 05:37:45.889: No driver found for USB device 8087:0020 140s (process:2905): libfprint-context-DEBUG: 05:37:45.889: No driver found for USB device 1D6B:0002 140s (process:2905): libfprint-device-DEBUG: 05:37:45.889: Device reported probe completion 140s (process:2905): libfprint-device-DEBUG: 05:37:45.889: Completing action FPI_DEVICE_ACTION_PROBE in idle! 140s (process:2905): libfprint-device-DEBUG: 05:37:45.889: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 140s (process:2905): libfprint-image_device-DEBUG: 05:37:45.891: Image device open completed 140s (process:2905): libfprint-device-DEBUG: 05:37:45.891: Device reported open completion 140s (process:2905): libfprint-device-DEBUG: 05:37:45.891: Completing action FPI_DEVICE_ACTION_OPEN in idle! 140s (process:2905): libfprint-device-DEBUG: 05:37:45.891: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 140s (process:2905): libfprint-device-DEBUG: 05:37:45.891: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 140s (process:2905): libfprint-image_device-DEBUG: 05:37:45.891: Activating image device 140s (process:2905): libfprint-image_device-DEBUG: 05:37:45.891: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 140s (process:2905): libfprint-SSM-DEBUG: 05:37:45.891: [vfs301] 1 entering state 0 140s (process:2905): libfprint-SSM-DEBUG: 05:37:45.959: [vfs301] 1 completed successfully 140s (process:2905): libfprint-image_device-DEBUG: 05:37:45.959: Image device activation completed 140s (process:2905): libfprint-image_device-DEBUG: 05:37:45.959: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 140s (process:2905): libfprint-image_device-DEBUG: 05:37:45.959: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 140s (process:2905): libfprint-SSM-DEBUG: 05:37:45.959: [vfs301] M_LOOP_NUM_STATES entering state 0 140s (process:2905): libfprint-SSM-DEBUG: 05:37:45.961: [vfs301] M_LOOP_NUM_STATES entering state 1 140s (process:2905): libfprint-device-DEBUG: 05:37:45.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED 141s (process:2905): libfprint-device-DEBUG: 05:37:45.991: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.161: [vfs301] M_LOOP_NUM_STATES entering state 2 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.163: [vfs301] M_LOOP_NUM_STATES entering state 1 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.363: [vfs301] M_LOOP_NUM_STATES entering state 2 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.365: [vfs301] M_LOOP_NUM_STATES entering state 3 141s (process:2905): libfprint-device-DEBUG: 05:37:46.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.365: Image device reported finger status: on 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.365: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.366: [vfs301] M_LOOP_NUM_STATES entering state 4 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.566: [vfs301] M_LOOP_NUM_STATES entering state 5 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.570: [vfs301] M_LOOP_NUM_STATES entering state 6 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.571: Image device captured an image 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 141s (process:2905): libfprint-device-DEBUG: 05:37:46.572: Device reported finger status change: FP_FINGER_STATUS_PRESENT 141s (process:2905): libfprint-SSM-DEBUG: 05:37:46.572: [vfs301] M_LOOP_NUM_STATES completed successfully 141s (process:2905): libfprint-device-DEBUG: 05:37:46.572: Device reported finger status change: FP_FINGER_STATUS_NONE 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Image device reported finger status: off 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Deactivating image device 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Image device deactivation completed 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.572: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 141s (process:2905): libfprint-image-DEBUG: 05:37:46.592: Minutiae scan completed in 0.019715 secs 141s (process:2905): libfprint-device-DEBUG: 05:37:46.592: Device reported capture completion 141s (process:2905): libfprint-device-DEBUG: 05:37:46.592: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 141s (process:2905): libfprint-device-DEBUG: 05:37:46.592: Updated temperature model after 0.60 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 141s (process:2905): libfprint-image_device-DEBUG: 05:37:46.593: Image device close completed 141s (process:2905): libfprint-device-DEBUG: 05:37:46.593: Device reported close completion 141s (process:2905): libfprint-device-DEBUG: 05:37:46.593: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 141s (process:2905): libfprint-device-DEBUG: 05:37:46.593: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 141s ** (umockdev-run:2901): DEBUG: 05:37:46.695: umockdev.vala:154: Removing test bed /tmp/umockdev.4O6212 141s (umockdev-run:2901): GLib-DEBUG: 05:37:46.704: unsetenv() is not thread-safe and should not be used after threads are created 141s Comparing PNGs /tmp/libfprint-umockdev-test-th2yziqq/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 141s PASS: libfprint-2/driver-vfs301.test 141s Running test: libfprint-2/driver-egis0570.test 141s ** (umockdev-run:2914): DEBUG: 05:37:46.771: umockdev.vala:127: Created udev test bed /tmp/umockdev.44D312 141s ** (umockdev-run:2914): DEBUG: 05:37:46.771: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 141s ** (umockdev-run:2914): DEBUG: 05:37:46.773: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 141s ** (umockdev-run:2914): DEBUG: 05:37:46.777: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.44D312/dev/bus/usb/001/005 141s ** (umockdev-run:2914): DEBUG: 05:37:46.777: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 141s ** (umockdev-run:2914): DEBUG: 05:37:46.778: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 141s ** (umockdev-run:2914): DEBUG: 05:37:46.781: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.44D312/dev/bus/usb/001/001 141s ** (umockdev-run:2914): DEBUG: 05:37:46.782: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 141s ** (umockdev-run:2914): DEBUG: 05:37:46.782: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 141s (process:2918): libfprint-context-DEBUG: 05:37:46.908: Initializing FpContext (libfprint version 1.94.9+tod1) 141s (process:2918): libfprint-tod-DEBUG: 05:37:46.908: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 141s (process:2918): libfprint-context-DEBUG: 05:37:46.911: No driver found for USB device 1D6B:0002 141s (process:2918): libfprint-device-DEBUG: 05:37:46.911: Device reported probe completion 141s (process:2918): libfprint-device-DEBUG: 05:37:46.911: Completing action FPI_DEVICE_ACTION_PROBE in idle! 141s (process:2918): libfprint-device-DEBUG: 05:37:46.911: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 141s (process:2918): libfprint-image_device-DEBUG: 05:37:46.913: Image device open completed 141s (process:2918): libfprint-device-DEBUG: 05:37:46.913: Device reported open completion 141s (process:2918): libfprint-device-DEBUG: 05:37:46.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 141s (process:2918): libfprint-device-DEBUG: 05:37:46.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 141s (process:2918): libfprint-device-DEBUG: 05:37:46.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 141s (process:2918): libfprint-image_device-DEBUG: 05:37:46.913: Activating image device 141s (process:2918): libfprint-image_device-DEBUG: 05:37:46.913: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.913: [egis0570] SM_STATES_NUM entering state 0 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.913: [egis0570] SM_STATES_NUM entering state 1 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.913: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-image_device-DEBUG: 05:37:46.914: Image device activation completed 141s (process:2918): libfprint-image_device-DEBUG: 05:37:46.914: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 141s (process:2918): libfprint-image_device-DEBUG: 05:37:46.914: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 141s (process:2918): libfprint-device-DEBUG: 05:37:46.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.914: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.914: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.915: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.916: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.917: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.917: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.918: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.918: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.919: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.920: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.921: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.921: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.922: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.922: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.923: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.924: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.925: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.925: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.926: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.926: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.927: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.927: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.928: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.928: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.929: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.930: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.930: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.931: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.932: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.932: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.933: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.933: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.934: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.934: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.935: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.935: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.936: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.937: [egis0570] SM_STATES_NUM entering state 2 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.938: [egis0570] SM_STATES_NUM entering state 3 141s (process:2918): libfprint-SSM-DEBUG: 05:37:46.938: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.939: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.939: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.940: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.940: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.941: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.941: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.942: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.942: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.942: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.942: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.943: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.943: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.944: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.944: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.945: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.945: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.946: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.946: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.947: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.947: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.947: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.947: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.947: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.947: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.947: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.947: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.947: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.948: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.948: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.949: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.949: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.950: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.951: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.951: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.952: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.952: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.952: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.952: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.952: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.952: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.952: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.952: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.952: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.952: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.953: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.953: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.954: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.954: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.955: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.956: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.957: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.957: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.957: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.957: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.957: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.957: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.957: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.957: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.957: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.957: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.957: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.958: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.958: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.959: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.960: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.961: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.961: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.962: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.962: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.963: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.963: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.963: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.963: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.963: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.963: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.963: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.963: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.963: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.964: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.964: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.965: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.965: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.966: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.966: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.967: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.967: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.968: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.968: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.968: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.968: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.968: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.968: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.968: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.968: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.968: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.969: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.969: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.970: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.970: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.971: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.972: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.973: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.973: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.973: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.973: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.973: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.973: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.973: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.973: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.973: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.974: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.974: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.974: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.974: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.975: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.976: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.977: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.977: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.978: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.978: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.979: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.979: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.979: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.979: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.979: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.979: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.979: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.979: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.979: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.979: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.980: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.980: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.981: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.982: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.982: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.983: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.983: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.984: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.984: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.984: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.984: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.984: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.984: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.984: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.984: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.984: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.984: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.985: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.986: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.986: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.988: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.988: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.989: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.989: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.990: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.990: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.990: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.990: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.990: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.990: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.990: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.990: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.990: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.991: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.991: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.992: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.992: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.993: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.994: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.995: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.995: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.995: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.995: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.996: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.996: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:46.996: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:46.996: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.996: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.996: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.996: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.996: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.997: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.997: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.998: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.999: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:46.999: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.001: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.001: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.002: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.002: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.002: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.002: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.002: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.002: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.002: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.002: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.002: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.002: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.003: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.004: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.004: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.005: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.005: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.006: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.006: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.007: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.007: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.007: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.007: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.007: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.007: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.007: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.007: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.007: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.007: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.008: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.008: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.009: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.010: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.010: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.011: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.011: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.012: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.012: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.012: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.012: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.012: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.012: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.012: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.012: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.012: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.012: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.013: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-device-DEBUG: 05:37:47.013: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.014: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.014: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.015: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.015: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.016: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.016: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.017: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.017: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.017: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.017: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.017: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.017: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.017: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.017: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.017: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.018: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.018: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.019: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.019: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.020: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.020: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.021: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.021: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.022: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.022: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.022: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.022: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.022: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.022: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.022: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.022: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.022: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.023: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.023: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.024: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.024: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.025: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.025: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.026: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.026: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.027: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.027: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.027: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.027: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.027: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.027: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.027: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.027: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.027: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.028: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.028: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.029: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.030: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.031: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.031: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.032: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.032: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.033: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.033: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.033: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.033: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.033: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.033: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.033: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.033: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.033: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.034: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.034: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.035: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.035: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.037: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.037: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.038: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.038: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.039: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.039: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.039: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.039: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.039: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.039: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.039: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.039: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.039: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.040: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.040: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.041: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.042: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.043: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.043: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.044: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.044: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.044: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.044: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.044: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.044: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.044: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.045: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.045: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.045: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.045: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.045: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.045: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.046: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.047: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.047: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.048: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.049: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.049: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.049: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.049: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.050: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.050: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.050: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.050: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.050: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.050: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.050: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.050: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.050: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.051: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.052: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.053: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.053: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.054: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.054: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.055: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.055: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.055: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.055: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.055: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.055: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.055: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.055: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.055: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.056: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.056: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.058: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.058: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.059: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.059: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.060: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.060: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.061: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.061: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.061: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.061: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.061: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.061: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.061: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.061: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.061: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.062: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.062: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.063: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.063: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.064: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.065: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.065: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.065: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.066: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.066: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.066: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.066: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.066: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.066: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.066: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.066: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.066: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.067: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.067: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.068: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.068: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.069: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.070: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.071: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.071: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.071: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.071: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.071: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.071: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.071: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.071: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.071: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.071: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.071: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.072: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.072: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.073: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.073: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.074: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.074: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.077: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.077: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.078: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.078: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.078: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.078: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.078: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.078: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.078: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.078: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.078: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.079: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.079: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.080: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.080: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.082: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.082: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.083: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.083: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.084: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.084: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.084: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.084: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.084: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.084: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.084: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.084: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.084: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.084: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.085: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.085: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.086: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.087: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.087: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.088: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.088: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.089: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.089: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.089: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.089: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.089: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.089: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.089: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.089: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.089: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.089: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.090: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.091: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.091: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.092: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.092: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.093: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.093: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.094: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.094: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.094: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.094: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.094: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.094: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.094: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.094: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.094: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.095: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.095: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.096: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.097: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.098: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.098: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.099: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.099: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.100: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.100: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.100: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.100: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.100: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.100: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.100: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.100: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.100: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.100: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.101: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.102: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.102: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.103: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.103: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.104: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.104: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.105: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.105: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.105: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.105: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.105: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.105: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.105: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.105: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.105: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.106: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.106: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.107: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.107: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.108: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.109: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.110: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.110: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.111: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.111: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.111: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.111: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.111: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.111: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.111: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.111: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.111: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.111: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.112: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.113: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.113: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.114: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.115: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.116: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.116: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.116: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.117: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.117: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.117: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.117: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.117: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.117: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.117: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.117: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.117: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.118: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.119: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.119: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.120: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.120: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.122: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.122: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.122: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.122: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.122: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.122: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.122: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.122: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.122: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.122: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.122: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.123: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.123: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.124: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.125: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.126: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.126: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.127: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.127: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.128: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.128: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.128: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.128: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.128: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.128: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.128: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.128: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.128: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.128: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.128: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.129: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.130: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.130: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.131: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.133: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.133: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.134: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.134: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.134: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.134: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.134: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.134: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.134: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.134: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.134: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.135: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.135: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.136: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.136: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.137: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.138: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.139: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.139: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.139: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.139: Finger status (picture number, mean) : 1 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.139: Finger status (picture number, mean) : 2 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.139: Finger status (picture number, mean) : 3 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.139: Finger status (picture number, mean) : 4 , 0 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.139: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.139: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.139: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.139: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.140: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.140: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.141: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.142: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.142: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.143: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.144: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.144: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.144: Finger status (picture number, mean) : 0 , 0 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.144: Finger status (picture number, mean) : 1 , 1 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.144: Finger status (picture number, mean) : 2 , 2 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.144: Finger status (picture number, mean) : 3 , 3 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.144: Finger status (picture number, mean) : 4 , 6 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.144: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.144: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.144: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.144: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.145: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.145: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.146: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.146: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.147: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.148: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.149: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.149: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.149: Finger status (picture number, mean) : 0 , 11 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.149: Finger status (picture number, mean) : 1 , 16 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.149: Finger status (picture number, mean) : 2 , 23 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.149: Finger status (picture number, mean) : 3 , 28 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.149: Finger status (picture number, mean) : 4 , 32 142s (process:2918): libfprint-device-DEBUG: 05:37:47.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.149: Image device reported finger status: on 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.149: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 142s (process:2918): libfprint-device-DEBUG: 05:37:47.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.149: Image device reported finger status: off 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.149: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.149: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.149: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.150: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.150: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.151: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.152: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.153: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.153: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.154: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.154: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.155: Finger status (picture number, mean) : 0 , 38 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.155: Finger status (picture number, mean) : 1 , 43 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.155: Finger status (picture number, mean) : 2 , 48 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.155: Finger status (picture number, mean) : 3 , 54 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.155: Finger status (picture number, mean) : 4 , 58 142s (process:2918): libfprint-device-DEBUG: 05:37:47.155: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.155: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.155: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.155: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.155: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.155: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.156: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.157: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.157: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.158: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.158: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.159: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.159: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.160: Finger status (picture number, mean) : 0 , 62 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.160: Finger status (picture number, mean) : 1 , 68 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.160: Finger status (picture number, mean) : 2 , 71 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.160: Finger status (picture number, mean) : 3 , 73 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.160: Finger status (picture number, mean) : 4 , 77 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.160: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.160: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.160: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.160: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.161: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.161: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.162: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.162: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.163: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.163: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.164: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.164: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.165: Finger status (picture number, mean) : 0 , 79 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.165: Finger status (picture number, mean) : 1 , 79 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.165: Finger status (picture number, mean) : 2 , 82 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.165: Finger status (picture number, mean) : 3 , 84 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.165: Finger status (picture number, mean) : 4 , 85 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.165: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.165: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.165: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.165: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.166: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.166: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.167: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.168: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.168: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.169: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.170: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.170: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.170: Finger status (picture number, mean) : 0 , 88 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.170: Finger status (picture number, mean) : 1 , 89 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.170: Finger status (picture number, mean) : 2 , 90 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.170: Finger status (picture number, mean) : 3 , 92 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.170: Finger status (picture number, mean) : 4 , 92 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.170: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.170: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.170: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.170: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.171: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.171: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.172: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.173: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.174: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.174: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.175: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.175: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.176: Finger status (picture number, mean) : 0 , 93 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.176: Finger status (picture number, mean) : 1 , 94 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.176: Finger status (picture number, mean) : 2 , 95 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.176: Finger status (picture number, mean) : 3 , 96 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.176: Finger status (picture number, mean) : 4 , 97 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.176: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.176: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.176: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.176: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.177: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.177: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.178: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.178: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.179: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.180: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.181: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.181: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.181: Finger status (picture number, mean) : 0 , 97 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.181: Finger status (picture number, mean) : 1 , 95 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.181: Finger status (picture number, mean) : 2 , 95 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.181: Finger status (picture number, mean) : 3 , 96 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.181: Finger status (picture number, mean) : 4 , 97 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.181: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.181: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.181: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.181: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.182: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.182: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.183: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.184: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.184: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.185: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.186: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.186: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.186: Finger status (picture number, mean) : 0 , 96 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.186: Finger status (picture number, mean) : 1 , 97 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.186: Finger status (picture number, mean) : 2 , 98 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.186: Finger status (picture number, mean) : 3 , 98 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.186: Finger status (picture number, mean) : 4 , 98 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.186: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.186: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.186: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.186: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.187: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.187: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.188: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.189: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.190: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.190: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.191: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.191: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.192: Finger status (picture number, mean) : 0 , 98 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.192: Finger status (picture number, mean) : 1 , 99 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.192: Finger status (picture number, mean) : 2 , 100 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.192: Finger status (picture number, mean) : 3 , 99 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.192: Finger status (picture number, mean) : 4 , 97 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.192: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.192: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.192: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.192: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.192: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.193: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.194: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.194: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.195: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.195: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.196: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.196: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.197: Finger status (picture number, mean) : 0 , 98 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.197: Finger status (picture number, mean) : 1 , 98 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.197: Finger status (picture number, mean) : 2 , 98 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.197: Finger status (picture number, mean) : 3 , 95 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.197: Finger status (picture number, mean) : 4 , 91 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.197: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.197: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.197: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.197: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.197: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.198: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.199: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.199: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.200: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.200: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.201: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.201: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.202: Finger status (picture number, mean) : 0 , 88 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.202: Finger status (picture number, mean) : 1 , 88 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.202: Finger status (picture number, mean) : 2 , 88 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.202: Finger status (picture number, mean) : 3 , 87 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.202: Finger status (picture number, mean) : 4 , 89 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.202: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.202: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.202: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.202: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.203: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.203: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.204: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.204: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.205: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.205: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.206: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.206: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.207: Finger status (picture number, mean) : 0 , 88 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.207: Finger status (picture number, mean) : 1 , 89 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.207: Finger status (picture number, mean) : 2 , 90 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.207: Finger status (picture number, mean) : 3 , 91 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.207: Finger status (picture number, mean) : 4 , 89 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.207: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.207: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.207: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.207: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.208: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.208: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.209: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.209: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.210: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.210: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.212: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.212: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.212: Finger status (picture number, mean) : 0 , 90 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.212: Finger status (picture number, mean) : 1 , 89 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.212: Finger status (picture number, mean) : 2 , 85 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.212: Finger status (picture number, mean) : 3 , 75 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.212: Finger status (picture number, mean) : 4 , 46 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.212: Image device reported finger status: on 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.212: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.212: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.212: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.213: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.214: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.214: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.215: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.216: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.216: [egis0570] SM_STATES_NUM entering state 2 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.217: [egis0570] SM_STATES_NUM entering state 3 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.217: [egis0570] SM_STATES_NUM entering state 4 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.218: Finger status (picture number, mean) : 0 , 17 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.218: Finger status (picture number, mean) : 1 , 14 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.218: Finger status (picture number, mean) : 2 , 15 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.218: Finger status (picture number, mean) : 3 , 15 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.218: Finger status (picture number, mean) : 4 , 15 142s (process:2918): libfprint-assembling-DEBUG: 05:37:47.283: calc delta completed in 0.065224 secs 142s (process:2918): libfprint-assembling-DEBUG: 05:37:47.346: calc delta completed in 0.062832 secs 142s (process:2918): libfprint-assembling-DEBUG: 05:37:47.346: errors: 10243 rev: 29954 142s (process:2918): libfprint-assembling-DEBUG: 05:37:47.410: calc delta completed in 0.063685 secs 142s (process:2918): libfprint-assembling-DEBUG: 05:37:47.410: height is 292 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.412: Image device captured an image 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.413: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 142s (process:2918): libfprint-device-DEBUG: 05:37:47.416: Device reported finger status change: FP_FINGER_STATUS_PRESENT 142s (process:2918): libfprint-device-DEBUG: 05:37:47.416: Device reported finger status change: FP_FINGER_STATUS_NONE 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.416: Image device reported finger status: off 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.416: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.416: Deactivating image device 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.416: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.416: [egis0570] SM_STATES_NUM entering state 5 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.416: [egis0570] SM_STATES_NUM entering state 1 142s (process:2918): libfprint-egis0570-DEBUG: 05:37:47.416: deactivating, marking completed 142s (process:2918): libfprint-SSM-DEBUG: 05:37:47.416: [egis0570] SM_STATES_NUM completed successfully 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.416: Image device deactivation completed 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.416: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 142s (process:2918): libfprint-image-DEBUG: 05:37:47.463: Minutiae scan completed in 0.050235 secs 142s (process:2918): libfprint-device-DEBUG: 05:37:47.464: Device reported capture completion 142s (process:2918): libfprint-device-DEBUG: 05:37:47.464: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 142s (process:2918): libfprint-device-DEBUG: 05:37:47.464: Updated temperature model after 0.45 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 142s (process:2918): libfprint-image_device-DEBUG: 05:37:47.464: Image device close completed 142s (process:2918): libfprint-device-DEBUG: 05:37:47.464: Device reported close completion 142s (process:2918): libfprint-device-DEBUG: 05:37:47.464: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 142s (process:2918): libfprint-device-DEBUG: 05:37:47.464: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 142s ** (umockdev-run:2914): DEBUG: 05:37:47.811: umockdev.vala:154: Removing test bed /tmp/umockdev.44D312 142s (umockdev-run:2914): GLib-DEBUG: 05:37:47.822: unsetenv() is not thread-safe and should not be used after threads are created 142s Comparing PNGs /tmp/libfprint-umockdev-test-y3t4cpyr/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 142s PASS: libfprint-2/driver-egis0570.test 142s Running test: libfprint-2/driver-aes2501.test 142s ** (umockdev-run:2927): DEBUG: 05:37:47.945: umockdev.vala:127: Created udev test bed /tmp/umockdev.WRK912 142s ** (umockdev-run:2927): DEBUG: 05:37:47.945: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 142s ** (umockdev-run:2927): DEBUG: 05:37:47.949: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 142s ** (umockdev-run:2927): DEBUG: 05:37:47.954: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WRK912/dev/bus/usb/001/044 142s ** (umockdev-run:2927): DEBUG: 05:37:47.954: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 142s ** (umockdev-run:2927): DEBUG: 05:37:47.957: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 142s ** (umockdev-run:2927): DEBUG: 05:37:47.962: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WRK912/dev/bus/usb/001/001 142s ** (umockdev-run:2927): DEBUG: 05:37:47.962: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 142s ** (umockdev-run:2927): DEBUG: 05:37:47.962: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 143s (process:2931): libfprint-context-DEBUG: 05:37:48.078: Initializing FpContext (libfprint version 1.94.9+tod1) 143s (process:2931): libfprint-tod-DEBUG: 05:37:48.078: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 143s (process:2931): libfprint-context-DEBUG: 05:37:48.080: No driver found for USB device 1D6B:0002 143s (process:2931): libfprint-device-DEBUG: 05:37:48.080: Device reported probe completion 143s (process:2931): libfprint-device-DEBUG: 05:37:48.080: Completing action FPI_DEVICE_ACTION_PROBE in idle! 143s (process:2931): libfprint-device-DEBUG: 05:37:48.080: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:2931): libfprint-image_device-DEBUG: 05:37:48.082: Image device open completed 143s (process:2931): libfprint-device-DEBUG: 05:37:48.082: Device reported open completion 143s (process:2931): libfprint-device-DEBUG: 05:37:48.082: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s (process:2931): libfprint-device-DEBUG: 05:37:48.082: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:2931): libfprint-device-DEBUG: 05:37:48.082: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:2931): libfprint-image_device-DEBUG: 05:37:48.082: Activating image device 143s (process:2931): libfprint-image_device-DEBUG: 05:37:48.082: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.082: [aes2501] ACTIVATE_NUM_STATES entering state 0 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.082: write 38 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.084: all registers written 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.084: [aes2501] ACTIVATE_NUM_STATES entering state 1 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.084: read data 1 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.085: [aes2501] ACTIVATE_NUM_STATES entering state 2 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.085: write 7 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.086: all registers written 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.086: [aes2501] ACTIVATE_NUM_STATES entering state 3 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.086: 88926148: ../libfprint/drivers/aes2501.c:140 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.086: write 1 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.087: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.088: reg 0xaf = 20 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.088: [aes2501] ACTIVATE_NUM_STATES entering state 5 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.088: write 7 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.088: all registers written 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.088: [aes2501] ACTIVATE_NUM_STATES entering state 6 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.088: write 16 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.089: all registers written 143s (process:2931): libfprint-SSM-DEBUG: 05:37:48.089: [aes2501] ACTIVATE_NUM_STATES completed successfully 143s (process:2931): libfprint-image_device-DEBUG: 05:37:48.089: Image device activation completed 143s (process:2931): libfprint-image_device-DEBUG: 05:37:48.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:2931): libfprint-image_device-DEBUG: 05:37:48.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 143s (process:2931): libfprint-device-DEBUG: 05:37:48.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.089: 88929223: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.089: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.091: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.092: 88931922: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.092: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.094: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.095: 88934817: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.095: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.097: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.098: 88937720: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.098: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.100: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.100: 88940333: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.100: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.102: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.103: 88943255: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.103: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.106: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.107: 88946545: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.107: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.109: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.110: 88949850: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.110: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.112: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.113: 88953055: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.113: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.115: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.116: 88956150: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.116: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.118: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.119: 88959327: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.119: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.122: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.123: 88962552: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.123: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.126: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.127: 88966972: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.127: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.129: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.130: 88969585: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.130: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.132: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.132: 88972422: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.132: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.134: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.135: 88975025: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.135: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.137: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.138: 88977719: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.138: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.139: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.140: 88980029: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.140: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.142: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.143: 88982650: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.143: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.145: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.145: 88985268: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.145: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.147: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.148: 88987602: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.148: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.149: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.150: 88989996: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.150: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.152: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.153: 88992583: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.153: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.154: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.155: 88995169: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.155: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.157: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.158: 88997718: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.158: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.160: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.160: 89000464: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.161: write 23 regs 143s Executing: libfprint-2/driver-aes2501.test 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.162: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.163: 89002879: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.163: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.165: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.166: 89005704: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.166: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.168: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.168: 89008387: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.168: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.170: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.171: 89010925: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.171: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.173: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.173: 89013430: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.173: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.175: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.176: 89015911: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.176: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.178: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.178: 89018340: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.178: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.180: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.181: 89020727: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.181: write 23 regs 143s (process:2931): libfprint-device-DEBUG: 05:37:48.182: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.183: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.183: 89023167: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.183: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.185: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.186: 89025643: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.186: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.188: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.188: 89028372: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.188: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.191: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.192: 89031705: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.192: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.194: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.195: 89035061: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.195: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.198: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.199: 89038530: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.199: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.201: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.202: 89041763: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.202: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.204: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.205: 89044674: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.205: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.207: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.208: 89047717: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.208: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.210: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.211: 89050869: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.211: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.213: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.214: 89053752: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.214: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.216: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.217: 89056948: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.217: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.219: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.220: 89059948: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.220: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.222: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.223: 89062837: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.223: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.225: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.233: 89073217: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.233: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.235: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.236: 89075907: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.236: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.238: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.238: 89078472: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.239: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.240: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.241: 89081173: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.241: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.244: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.245: 89085080: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.245: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.247: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.248: 89087811: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.248: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.250: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.250: 89090417: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.250: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.252: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.253: 89092894: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.253: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.255: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.255: 89095460: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.255: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.258: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.258: 89098298: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.258: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.260: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.261: 89101293: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.261: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.263: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.264: 89104027: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.264: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.266: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.267: 89106577: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.267: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.269: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.269: 89109183: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.269: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.271: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.272: 89111773: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.272: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.274: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.274: 89114364: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.274: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.276: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.277: 89116897: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.277: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.279: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.279: 89119443: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.279: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.281: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.282: 89121960: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.282: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.284: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.284: 89124451: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.284: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.287: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.287: 89127147: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.287: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.289: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.290: 89129950: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.290: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.292: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.293: 89132505: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.293: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.294: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.295: 89135161: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.295: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.297: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.298: 89137821: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.298: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.300: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.300: 89140268: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.300: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.302: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.303: 89142895: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.303: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.305: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.305: 89145327: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.305: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.307: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.308: 89147751: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.308: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.310: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.310: 89150204: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.310: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.312: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.313: 89152629: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.313: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.314: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.315: 89155031: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.315: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.317: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.318: 89157502: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.318: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.319: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.320: 89160016: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.320: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.322: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.323: 89162660: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.323: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.325: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.325: 89165247: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.325: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.327: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.328: 89167788: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.328: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.330: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.330: 89170262: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.330: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.332: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.333: 89172878: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.333: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.335: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.336: 89175755: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.336: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.338: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.338: 89178239: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.338: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.340: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.341: 89180707: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.341: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.343: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.343: 89183245: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.343: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.345: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.346: 89185858: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.346: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.348: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.348: 89188386: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.348: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.350: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.351: 89190864: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.351: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.353: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.353: 89193273: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.353: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.355: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.356: 89195643: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.356: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.357: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.358: 89198029: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.358: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.360: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.360: 89200465: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.361: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.362: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.363: 89203002: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.363: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.365: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.366: 89205534: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.366: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.367: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.368: 89208049: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.368: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.370: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.371: 89210530: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.371: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.372: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.373: 89213083: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.373: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.375: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.376: 89215484: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.376: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.377: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.378: 89218059: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.378: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.380: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.381: 89220651: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.381: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.383: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.384: 89223795: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.384: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.386: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.387: 89226862: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.387: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.390: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.391: 89231034: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.391: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.394: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.396: 89235805: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.396: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.399: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.401: 89240691: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.401: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.405: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.406: 89245887: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.406: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.409: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.410: 89250163: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.410: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.413: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.415: 89254560: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.415: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.419: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.420: 89259827: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.420: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.424: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.429: 89269274: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.429: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.433: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.434: 89273733: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.434: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.437: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.438: 89277646: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.438: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.440: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.445: 89285240: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.445: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.447: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.448: 89288234: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.448: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.452: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.452: 89292328: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.452: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.456: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.456: 89296363: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.456: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.459: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.460: 89300050: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.460: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.463: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.464: 89303725: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.464: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.466: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.467: 89306698: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.467: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.469: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.469: 89309427: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.470: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.471: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.472: 89312072: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.472: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.474: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.475: 89314748: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.475: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.477: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.477: 89317445: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.477: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.479: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.480: 89319971: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.480: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.482: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.483: 89322801: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.483: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.485: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.485: 89325380: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.485: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.487: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.488: 89328126: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.488: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.490: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.491: 89330868: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.491: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.493: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.493: 89333468: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.494: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.495: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.496: 89336068: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.496: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.498: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.499: 89338678: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.499: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.501: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.501: 89341320: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.501: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.503: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.504: 89343940: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.504: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.506: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.507: 89346505: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.507: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.508: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.509: 89349117: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.509: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.511: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.512: 89351971: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.512: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.514: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.515: 89354684: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.515: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.517: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.518: 89357680: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.518: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.520: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.521: 89360768: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.521: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.523: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.523: 89363427: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.523: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.525: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.526: 89366083: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.526: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.528: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.529: 89368686: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.529: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.531: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.531: 89371368: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.531: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.534: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.534: 89374291: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.534: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.536: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.537: 89376984: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.537: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.539: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.540: 89379704: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.540: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.542: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.543: 89382628: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.543: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.545: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.545: 89385423: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.545: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.547: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.548: 89388031: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.548: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.550: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.551: 89390619: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.551: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.553: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.553: 89393365: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.553: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.555: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.556: 89395924: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.556: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.562: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.563: 89402745: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.563: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.565: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.565: 89405463: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.566: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.567: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.568: 89408029: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.568: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.570: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.571: 89410625: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.571: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.573: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.574: 89413663: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.574: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.576: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.576: 89416460: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.577: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.578: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.579: 89419144: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.579: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.581: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.582: 89422092: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.582: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.584: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.585: 89424974: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.585: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.587: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.588: 89427789: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.588: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.590: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.591: 89430688: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.591: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.593: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.594: 89433601: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.594: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.596: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.596: 89436254: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.596: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.598: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.599: 89439032: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.599: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.601: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.602: 89442093: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.602: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.604: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.605: 89445167: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.605: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.607: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.608: 89447808: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.608: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.614: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.615: 89454799: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.615: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.617: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.618: 89457678: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.618: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.620: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.621: 89460505: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.621: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.623: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.623: 89463220: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.623: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.625: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.626: 89466205: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.626: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.629: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.630: 89470191: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.630: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.633: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.633: 89473312: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.633: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.635: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.636: 89475741: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.636: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.638: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.638: 89478412: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.638: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.640: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.641: 89480923: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.641: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.643: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.644: 89483505: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.644: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.645: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.646: 89486000: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.646: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.648: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.648: 89488448: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.648: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.650: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.651: 89491079: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.651: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.653: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.654: 89493674: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.654: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.656: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.656: 89496338: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.656: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.658: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.659: 89499103: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.659: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.662: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.662: 89502406: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.662: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.664: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.665: 89504942: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.665: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.668: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.669: 89508982: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.669: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.672: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.673: 89512721: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.673: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.675: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.676: 89516041: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.676: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.679: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.679: 89519448: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.680: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.682: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.683: 89522602: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.683: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.686: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.687: 89526517: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.687: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.689: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.690: 89530449: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.690: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.693: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.694: 89533973: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.694: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.696: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.697: 89537395: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.697: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.700: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.701: 89541131: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.701: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.704: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.705: 89544805: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.705: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.708: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.709: 89548592: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.709: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.715: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.716: 89555768: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.716: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.718: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.718: 89558223: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.718: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.720: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.721: 89560748: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.721: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.723: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.723: 89563456: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.723: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.725: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.726: 89566120: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.726: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.728: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.729: 89568896: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.729: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.731: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.732: 89571572: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.732: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.734: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.734: 89574435: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.734: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.737: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.737: 89577458: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.737: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.739: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.741: 89581296: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.741: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.743: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.744: 89584036: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.744: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.746: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.747: 89586548: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.747: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.748: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.749: 89589122: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.749: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.751: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.752: 89591702: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.752: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.755: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.756: 89595542: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.756: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.758: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.758: 89598374: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.758: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.760: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.761: 89601091: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.761: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.764: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.765: 89604859: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.765: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.767: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.767: 89607307: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.767: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.769: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.770: 89610047: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.770: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.772: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.773: 89612630: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.773: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.775: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.775: 89615213: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.775: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.777: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.778: 89617779: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.778: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.780: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.780: 89620210: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.780: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.782: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.783: 89623181: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.783: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.785: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.786: 89625791: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.786: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.788: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.788: 89628293: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.788: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.790: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.791: 89630672: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.791: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.793: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.793: 89633313: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.793: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.795: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.796: 89636056: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.796: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.798: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.799: 89638780: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.799: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.801: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.801: 89641426: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.801: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.806: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.807: 89647054: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.807: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.809: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.810: 89649878: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.810: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.812: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.813: 89652729: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.813: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.815: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.816: 89655484: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.816: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.818: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.818: 89658293: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.818: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.820: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.821: 89661191: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.821: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.823: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.824: 89664153: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.824: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.826: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.827: 89666894: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.827: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.829: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.830: 89669781: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.830: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.832: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.833: 89672601: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.833: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.835: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.836: 89675733: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.836: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.838: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.839: 89678552: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.839: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.841: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.841: 89681412: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.841: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.843: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.844: 89684133: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.844: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.846: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.847: 89686991: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.847: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.849: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.850: 89689909: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.850: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.852: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.853: 89693091: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.853: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.855: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.856: 89696178: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.856: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.858: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.859: 89699141: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.859: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.861: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.862: 89702191: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.862: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.864: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.866: 89705578: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.866: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.868: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.869: 89708812: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.869: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.872: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.872: 89712438: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.873: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.875: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.877: 89716482: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.877: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.879: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.879: 89719444: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.879: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.882: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.883: 89722633: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.883: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.885: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.886: 89725683: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.886: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.888: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.889: 89728904: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.889: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.891: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.892: 89731817: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.892: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.894: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.895: 89734969: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.895: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.898: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.898: 89738384: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.898: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.901: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.901: 89741442: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.901: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.904: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.904: 89744288: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.904: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.906: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.907: 89747195: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.907: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.909: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.910: 89750011: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.910: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.913: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.914: 89753829: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.914: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.916: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.917: 89756964: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.917: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.919: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.920: 89759757: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.920: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.922: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.923: 89762575: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.923: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.925: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.926: 89765820: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.926: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.928: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.929: 89768637: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.929: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.931: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.931: 89771401: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.931: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.934: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.934: 89774371: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.934: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.936: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.937: 89777188: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.937: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.939: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.940: 89780167: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.940: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.942: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.943: 89783021: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.943: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.945: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.946: 89785831: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.946: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.948: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.949: 89788599: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.949: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.951: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.952: 89791580: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.952: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.954: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.954: 89794459: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.954: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.957: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.957: 89797294: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.957: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.959: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.960: 89800174: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.960: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.962: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.963: 89803175: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.963: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.965: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.966: 89806025: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.966: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.968: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.969: 89808780: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.969: write 23 regs 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.971: all registers written 143s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.972: 89811523: ../libfprint/drivers/aes2501.c:310 143s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.972: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.974: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.975: 89814499: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.975: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.976: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.977: 89817202: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.977: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.979: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.980: 89820056: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.980: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.982: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.983: 89823171: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.983: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.986: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.987: 89826885: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.987: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.989: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.990: 89829839: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.990: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.992: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.993: 89832934: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.993: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.995: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.996: 89835587: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.996: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.998: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:48.998: 89838438: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:48.998: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.000: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.001: 89841073: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.001: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.003: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.004: 89843626: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.004: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.006: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.006: 89846436: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.006: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.008: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.010: 89849529: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.010: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.012: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.013: 89853403: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.013: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.016: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.017: 89857109: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.017: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.021: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.022: 89861702: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.022: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.025: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.026: 89866089: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.026: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.029: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.030: 89870264: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.030: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.033: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.034: 89873756: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.034: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.036: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.037: 89877215: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.037: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.040: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.041: 89880959: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.041: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.044: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.045: 89885037: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.045: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.047: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.048: 89887948: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.048: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.050: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.051: 89890506: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.051: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.053: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.053: 89893326: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.053: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.056: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.057: 89896473: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.057: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.059: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.062: 89901935: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.062: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.064: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.065: 89904942: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.065: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.067: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.068: 89907766: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.068: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.070: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.071: 89911094: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.071: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.073: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.074: 89914028: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.074: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.076: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.077: 89917194: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.077: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.079: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.080: 89920045: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.080: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.082: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.083: 89923072: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.083: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.085: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.086: 89926238: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.086: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.089: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.089: 89929361: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.089: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.091: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.092: 89932263: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.092: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.095: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.095: 89935393: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.095: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.097: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.098: 89938070: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.098: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.100: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.101: 89940952: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.101: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.105: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.106: 89945489: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.106: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.108: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.109: 89948814: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.109: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.111: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.112: 89951604: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.112: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.114: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.114: 89954342: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.114: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.117: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.117: 89957379: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.117: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.120: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.121: 89960526: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.121: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.123: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.124: 89963683: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.124: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.126: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.126: 89966384: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.126: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.129: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.130: 89969728: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.130: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.132: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.132: 89972430: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.132: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.135: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.136: 89975574: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.136: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.138: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.139: 89979040: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.139: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.142: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.142: 89982233: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.142: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.144: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.145: 89985051: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.145: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.147: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.148: 89988106: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.148: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.150: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.151: 89991267: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.151: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.153: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.154: 89994276: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.154: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.157: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.157: 89997306: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.157: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.159: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.160: 89999953: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.160: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.162: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.163: 90003318: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.163: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.166: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.166: 90006467: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.167: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.169: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.170: 90009531: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.170: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.172: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.172: 90012367: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.172: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.175: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.175: 90015266: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.175: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.177: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.178: 90018172: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.178: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.180: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.181: 90020996: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.181: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.183: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.184: 90024051: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.184: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.186: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.187: 90026828: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.187: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.189: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.190: 90029777: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.190: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.192: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.193: 90032700: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.193: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.195: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.196: 90035725: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.196: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.198: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.199: 90038621: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.199: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.201: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.202: 90041834: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.202: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.204: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.205: 90044749: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.205: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.207: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.208: 90047625: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.208: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.210: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.211: 90050514: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.211: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.212: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.213: 90053029: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.213: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.215: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.216: 90055502: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.216: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.217: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.218: 90057763: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.218: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.220: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.220: 90060221: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.220: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.222: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.223: 90062730: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.223: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.224: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.225: 90065027: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.225: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.227: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.227: 90067393: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.227: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.229: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.230: 90070047: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.230: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.232: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.232: 90072407: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.232: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.234: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.235: 90074787: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.235: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.238: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.238: 90078425: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.238: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.240: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.241: 90080778: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.241: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.243: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.243: 90083265: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.243: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.245: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.246: 90085757: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.246: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.250: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.250: 90090439: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.250: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.252: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.253: 90093009: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.253: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.255: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.255: 90095453: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.255: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.257: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.258: 90097931: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.258: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.260: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.261: 90100498: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.261: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.262: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.263: 90102942: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.263: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.265: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.269: 90109345: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.269: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.271: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.272: 90111932: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.272: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.274: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.274: 90114266: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.274: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.276: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.277: 90116615: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.277: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.278: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.279: 90119043: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.279: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.281: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.281: 90121277: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.281: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.283: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.284: 90123608: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.284: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.285: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.286: 90126200: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.286: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.288: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.289: 90129056: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.289: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.291: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.291: 90131420: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.291: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.295: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.295: 90135305: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.295: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.298: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.299: 90138976: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.299: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.301: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.301: 90141279: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.301: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.304: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.305: 90144547: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.305: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.306: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.307: 90146878: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.307: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.310: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.310: 90150309: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.310: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.312: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.313: 90152592: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.313: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.314: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.315: 90155064: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.315: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.317: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.317: 90157469: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.318: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.319: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.320: 90159763: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.320: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.322: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.322: 90162320: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.322: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.324: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.325: 90164696: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.325: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.326: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.327: 90167030: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.327: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.329: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.330: 90169577: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.330: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.331: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.332: 90172035: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.332: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.334: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.334: 90174415: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.334: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.336: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.337: 90176818: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.337: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.339: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.339: 90179269: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.339: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.342: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.343: 90183182: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.343: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.345: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.346: 90185853: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.346: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.348: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.348: 90188170: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.348: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.350: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.351: 90190962: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.351: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.353: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.354: 90193531: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.354: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.355: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.356: 90196130: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.356: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.358: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.359: 90198874: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.359: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.361: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.362: 90201812: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.362: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.364: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.364: 90204144: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.364: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.366: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.367: 90206671: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.367: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.368: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.369: 90208986: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.369: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.371: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.372: 90211520: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.372: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.374: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.375: 90214578: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.375: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.377: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.377: 90217218: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.377: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.379: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.380: 90219836: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.380: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.382: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.382: 90222469: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.383: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.385: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.385: 90225324: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.385: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.387: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.388: 90228282: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.388: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.390: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.391: 90230970: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.391: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.393: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.393: 90233386: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.393: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.395: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.396: 90235875: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.396: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.398: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.398: 90238319: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.398: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.400: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.401: 90241021: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.401: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.403: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.404: 90243549: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.404: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.409: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.410: 90250074: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.410: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.412: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.412: 90252335: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.412: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.414: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.415: 90254767: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.415: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.417: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.417: 90257228: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.417: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.419: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.420: 90259607: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.420: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.421: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.422: 90261960: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.422: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.424: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.425: 90264651: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.425: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.426: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.427: 90267117: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.427: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.429: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.429: 90269415: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.429: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.431: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.432: 90271778: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.432: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.434: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.434: 90274093: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.434: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.436: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.436: 90276390: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.436: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.438: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.439: 90278819: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.439: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.442: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.443: 90282636: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.443: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.445: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.445: 90285359: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.445: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.447: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.448: 90287634: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.448: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.450: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.450: 90290208: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.450: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.452: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.453: 90292639: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.453: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.454: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.455: 90295014: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.455: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.457: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.458: 90297734: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.458: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.460: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.460: 90300386: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.460: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.462: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.463: 90302705: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.463: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.465: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.465: 90305155: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.465: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.467: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.468: 90307506: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.468: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.469: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.470: 90310008: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.470: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.472: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.473: 90312558: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.473: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.474: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.475: 90315127: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.475: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.477: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.478: 90317662: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.478: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.479: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.480: 90320120: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.480: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.482: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.483: 90322623: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.483: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.487: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.488: 90328010: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.488: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.490: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.491: 90330791: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.491: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.493: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.493: 90333303: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.493: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.495: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.496: 90335832: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.496: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.498: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.498: 90338239: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.498: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.500: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.501: 90340694: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.501: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.503: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.503: 90343129: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.503: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.505: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.506: 90345500: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.506: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.510: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.511: 90350601: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.511: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.512: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.513: 90352904: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.513: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.515: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.516: 90355624: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.516: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.518: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.518: 90358323: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.518: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.520: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.522: 90361896: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.522: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.524: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.524: 90364344: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.524: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.526: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.527: 90367083: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.527: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.529: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.530: 90369805: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.530: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.532: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.532: 90372419: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.532: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.534: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.535: 90375100: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.535: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.537: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.538: 90377689: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.538: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.540: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.540: 90380366: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.540: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.542: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.543: 90382976: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.543: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.545: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.545: 90385309: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.545: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.547: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.548: 90387708: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.548: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.550: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.551: 90390643: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.551: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.553: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.553: 90393344: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.553: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.555: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.556: 90395926: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.556: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.558: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.558: 90398342: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.558: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.560: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.561: 90400822: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.561: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.563: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.563: 90403313: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.563: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.565: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.566: 90405737: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.566: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.568: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.569: 90408919: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.569: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.571: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.572: 90411646: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.572: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.574: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.575: 90414622: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.575: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.576: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.577: 90416879: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.577: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.583: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.586: 90425950: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.586: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.588: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.588: 90428377: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.588: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.590: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.591: 90430966: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.591: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.593: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.594: 90433522: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.594: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.595: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.596: 90436173: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.596: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.602: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.606: 90445780: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.606: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.608: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.609: 90448657: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.609: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.611: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.612: 90451480: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.612: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.614: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.615: 90454609: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.615: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.617: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.618: 90457532: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.618: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.620: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.621: 90460700: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.621: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.623: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.624: 90463679: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.624: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.626: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.627: 90466568: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.627: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.629: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.629: 90469378: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.629: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.632: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.632: 90472377: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.632: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.634: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.635: 90474963: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.635: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.637: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.638: 90477521: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.638: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.639: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.640: 90480045: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.640: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.642: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.643: 90482632: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.643: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.645: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.645: 90485260: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.645: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.647: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.648: 90487915: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.648: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.651: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.652: 90491862: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.652: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.654: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.655: 90494582: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.655: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.657: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.657: 90497214: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.657: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.659: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.662: 90501825: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.662: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.664: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.665: 90504637: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.665: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.667: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.668: 90507600: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.668: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.670: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.670: 90510208: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.670: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.672: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.673: 90512720: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.673: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.675: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.675: 90515307: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.675: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.677: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.678: 90518238: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.678: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.680: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.681: 90520993: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.681: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.683: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.684: 90523818: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.684: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.690: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.691: 90530533: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.691: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.693: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.694: 90533630: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.694: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.696: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.696: 90536235: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.696: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.698: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.699: 90538785: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.699: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.701: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.701: 90541278: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.701: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.703: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.704: 90543997: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.704: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.706: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.707: 90546596: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.707: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.709: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.710: 90550237: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.710: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.712: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.713: 90553028: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.713: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.715: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.716: 90555693: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.716: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.718: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.718: 90558407: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.718: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.720: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.721: 90561191: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.721: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.723: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.724: 90563765: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.724: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.726: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.727: 90566724: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.727: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.729: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.729: 90569276: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.729: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.731: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.732: 90571952: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.732: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.734: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.735: 90574644: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.735: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.737: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.743: 90583412: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.744: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.748: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.749: 90588858: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.749: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.751: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.752: 90591497: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.752: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.753: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.754: 90594138: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.754: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.756: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.757: 90596595: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.757: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.759: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.759: 90599199: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.759: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.761: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.762: 90601839: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.762: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.767: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.768: 90607809: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.768: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.770: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.771: 90610879: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.771: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.773: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.774: 90613715: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.774: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.776: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.777: 90616584: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.777: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.779: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.780: 90619535: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.780: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.782: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.783: 90622560: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.783: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.785: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.786: 90625754: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.786: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.788: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.789: 90628936: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.789: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.791: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.792: 90631678: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.792: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.794: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.795: 90634605: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.795: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.797: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.798: 90637596: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.798: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.800: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.800: 90640265: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.800: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.802: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.803: 90642945: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.803: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.805: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.806: 90645516: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.806: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.807: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.808: 90648039: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.808: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.810: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.811: 90650873: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.811: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.813: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.814: 90653506: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.814: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.815: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.816: 90656231: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.816: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.818: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.819: 90659140: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.819: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.821: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.822: 90661514: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.822: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.823: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.824: 90663774: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.824: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.826: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.826: 90666260: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.826: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.828: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.829: 90668855: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.829: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.831: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.831: 90671246: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.831: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.833: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.834: 90673829: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.834: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.836: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.836: 90676331: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.836: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.838: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.839: 90679044: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.839: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.841: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.842: 90681876: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.842: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.844: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.844: 90684224: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.844: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.846: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.847: 90686887: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.847: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.849: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.850: 90689618: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.850: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.852: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.852: 90692356: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.852: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.854: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.855: 90694754: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.855: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.857: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.857: 90697307: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.857: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.859: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.860: 90700047: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.860: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.862: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.863: 90702571: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.863: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.865: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.865: 90705188: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.865: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.867: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.868: 90707679: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.868: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.869: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.870: 90710023: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.870: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.872: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.872: 90712466: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.873: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.874: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.875: 90714857: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.875: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.877: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.877: 90717303: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.877: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.879: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.880: 90719633: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.880: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.882: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.882: 90722240: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.882: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.884: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.885: 90724629: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.885: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.887: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.887: 90727181: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.887: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.889: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.890: 90729860: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.890: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.892: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.893: 90732601: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.893: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.895: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.896: 90735529: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.896: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.897: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.898: 90738248: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.898: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.900: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.901: 90740710: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.901: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.903: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.904: 90743673: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.904: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.906: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.906: 90746147: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.906: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.908: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.909: 90748739: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.909: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.911: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.911: 90751369: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.911: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.913: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.914: 90754232: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.914: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.916: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.917: 90756698: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.917: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.919: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.920: 90759470: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.920: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.921: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.922: 90762202: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.922: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.924: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.925: 90764822: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.925: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.927: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.928: 90767509: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.928: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.930: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.931: 90770718: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.931: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.933: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.934: 90773553: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.934: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.936: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.936: 90776399: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.936: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.940: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.941: 90780783: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.941: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.943: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.943: 90783351: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.943: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.948: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.950: 90789669: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.950: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.952: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.952: 90792386: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.952: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.955: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.956: 90795629: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.956: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.958: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.959: 90798606: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.959: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.961: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.962: 90801632: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.962: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.964: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.964: 90804305: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.964: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.966: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.967: 90806855: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.967: write 23 regs 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.970: all registers written 144s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.972: 90812232: ../libfprint/drivers/aes2501.c:310 144s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.972: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.974: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.975: 90815122: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.975: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.977: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.978: 90818271: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.978: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.986: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.987: 90826827: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.987: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.989: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.990: 90829954: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.990: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.992: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.993: 90833053: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.993: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.995: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.996: 90835982: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.996: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.998: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:49.999: 90838926: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:49.999: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.001: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.002: 90841777: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.002: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.004: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.005: 90845207: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.005: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.007: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.008: 90848280: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.008: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.011: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.011: 90851248: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.011: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.013: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.018: 90858089: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.018: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.020: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.021: 90861296: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.021: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.023: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.024: 90864205: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.024: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.026: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.027: 90866688: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.027: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.029: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.029: 90869418: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.029: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.032: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.032: 90872359: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.032: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.035: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.035: 90875285: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.035: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.037: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.038: 90878078: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.038: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.040: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.041: 90881126: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.041: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.043: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.044: 90884146: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.044: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.046: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.047: 90886863: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.047: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.049: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.050: 90889585: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.050: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.052: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.052: 90892424: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.052: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.058: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.059: 90899175: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.059: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.061: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.062: 90902197: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.062: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.064: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.065: 90904906: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.065: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.067: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.068: 90907534: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.068: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.070: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.070: 90910232: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.070: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.072: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.073: 90912767: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.073: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.075: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.075: 90915395: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.075: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.077: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.078: 90917911: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.078: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.080: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.081: 90920507: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.081: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.083: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.083: 90923403: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.083: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.086: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.086: 90926285: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.086: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.088: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.089: 90929080: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.089: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.091: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.092: 90931714: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.092: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.094: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.094: 90934422: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.094: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.097: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.098: 90937586: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.098: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.100: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.100: 90940189: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.100: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.102: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.103: 90943215: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.103: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.106: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.110: 90950375: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.110: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.113: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.114: 90953812: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.114: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.116: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.117: 90956800: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.117: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.119: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.120: 90959548: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.120: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.126: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.126: 90966458: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.127: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.131: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.131: 90971406: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.131: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.133: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.134: 90974056: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.134: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.136: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.137: 90976530: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.137: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.138: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.139: 90979169: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.139: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.141: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.142: 90981810: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.142: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.144: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.144: 90984282: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.144: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.146: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.147: 90986994: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.147: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.149: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.150: 90989909: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.150: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.152: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.153: 90993077: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.153: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.155: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.156: 90995763: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.156: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.162: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.162: 91002423: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.163: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.164: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.165: 91004978: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.165: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.171: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.172: 91011949: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.172: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.174: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.175: 91014881: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.175: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.177: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.178: 91018236: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.178: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.180: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.181: 91021290: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.181: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.183: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.184: 91024050: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.184: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.186: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.187: 91026769: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.187: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.189: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.189: 91029250: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.189: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.191: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.192: 91031759: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.192: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.194: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.194: 91034252: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.194: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.196: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.197: 91036647: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.197: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.198: all registers written 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.199: 91039124: ../libfprint/drivers/aes2501.c:310 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.199: write 23 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.201: all registers written 145s (process:2931): libfprint-device-DEBUG: 05:37:50.202: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.202: Image device reported finger status: on 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.202: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.202: 91041540: ../libfprint/drivers/aes2501.c:581 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.202: [aes2501] CAPTURE_NUM_STATES entering state 0 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.202: write 26 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.203: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.203: [aes2501] CAPTURE_NUM_STATES entering state 1 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.204: [aes2501] CAPTURE_NUM_STATES entering state 2 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.204: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.205: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.205: [aes2501] CAPTURE_NUM_STATES entering state 3 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.205: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.205: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.206: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.206: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.207: sum=5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.207: ADREFHI is 50 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.207: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.207: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.207: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.207: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.208: sum=8 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.208: ADREFHI is 48 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.208: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.208: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.208: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.208: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.209: sum=19 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.209: ADREFHI is 40 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.209: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.209: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.210: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.210: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.210: sum=60 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.210: ADREFHI is 38 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.210: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.210: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.211: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.211: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.212: sum=123 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.212: ADREFHI is 30 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.212: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.212: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.213: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.213: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.213: sum=226 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.213: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.213: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.213: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.214: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.214: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.215: sum=461 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.215: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.215: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.215: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.216: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.216: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.216: sum=466 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.216: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.216: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.216: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.217: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.217: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.218: sum=465 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.218: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.218: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.218: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.218: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.218: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.219: sum=620 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.219: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.219: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.219: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.220: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.220: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.220: sum=629 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.220: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.220: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.220: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.221: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.221: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.222: sum=615 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.222: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.222: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.222: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.222: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.222: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.223: sum=585 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.223: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.223: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.223: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.224: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.224: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.224: sum=581 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.224: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.224: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.224: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.225: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.225: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.225: sum=418 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.225: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.225: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.225: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.226: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.226: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.227: sum=406 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.227: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.227: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.227: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.228: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.228: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.228: sum=389 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.228: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.228: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.228: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.229: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.229: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.230: sum=388 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.230: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.230: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.230: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.230: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.230: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.231: sum=393 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.231: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.231: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.231: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.231: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.232: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.232: sum=389 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.232: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.232: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.232: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.233: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.233: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.234: sum=379 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.234: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.234: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.234: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.234: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.234: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.235: sum=361 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.235: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.235: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.235: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.236: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.236: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.236: sum=356 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.236: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.236: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.236: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.237: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.237: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.238: sum=193 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.238: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.238: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.238: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.238: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.238: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.239: sum=178 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.239: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.239: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.239: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.240: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.240: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.241: sum=164 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.241: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.241: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.241: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.241: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.241: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.242: sum=157 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.242: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.242: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.242: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.243: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.243: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.243: sum=152 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.243: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.243: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.243: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.244: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.244: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.245: sum=154 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.245: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.245: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.245: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.246: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.246: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.246: sum=157 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.246: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.246: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.246: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.247: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.247: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.248: sum=161 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.248: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.248: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.248: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.248: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.248: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.249: sum=161 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.249: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.249: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.249: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.250: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.250: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.250: sum=161 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.251: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.251: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.251: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.251: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.251: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.252: sum=162 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.252: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.252: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.252: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.253: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.253: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.253: sum=166 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.253: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.253: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.253: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.254: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.254: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.255: sum=143 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.255: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.255: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.255: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.255: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.255: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.256: sum=106 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.256: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.256: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.256: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.257: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.257: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.257: sum=74 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.257: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.257: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.257: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.258: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.258: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.259: sum=51 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.259: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.259: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.259: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.259: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.259: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.260: sum=40 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.260: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.260: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.260: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.262: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.262: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.263: sum=39 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.263: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.263: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.263: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.263: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.263: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.264: sum=19 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.264: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.264: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.264: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.265: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.265: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.265: sum=13 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.265: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.265: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.265: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.266: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.266: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.266: sum=5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.266: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.266: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.266: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.267: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.267: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.268: sum=2 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.268: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.268: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.268: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.268: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.268: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.272: sum=0 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.272: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.272: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.272: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.273: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.273: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.273: sum=0 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.274: ADREFHI is 28 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.274: [aes2501] CAPTURE_NUM_STATES entering state 4 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.274: write 7 regs 145s (process:2931): libfprint-aeslib-DEBUG: 05:37:50.274: all registers written 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.274: [aes2501] CAPTURE_NUM_STATES entering state 5 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.275: sum=0 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.275: ADREFHI is 28 145s (process:2931): libfprint-assembling-DEBUG: 05:37:50.366: calc delta completed in 0.090909 secs 145s (process:2931): libfprint-assembling-DEBUG: 05:37:50.458: calc delta completed in 0.092228 secs 145s (process:2931): libfprint-assembling-DEBUG: 05:37:50.459: errors: 53228 rev: 72653 145s (process:2931): libfprint-assembling-DEBUG: 05:37:50.558: calc delta completed in 0.099035 secs 145s (process:2931): libfprint-assembling-DEBUG: 05:37:50.558: height is 102 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.559: Image device captured an image 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.560: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 145s (process:2931): libfprint-device-DEBUG: 05:37:50.560: Device reported finger status change: FP_FINGER_STATUS_PRESENT 145s (process:2931): libfprint-device-DEBUG: 05:37:50.564: Device reported finger status change: FP_FINGER_STATUS_NONE 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.564: Image device reported finger status: off 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.564: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.564: Deactivating image device 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.564: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 145s (process:2931): libfprint-SSM-DEBUG: 05:37:50.564: [aes2501] CAPTURE_NUM_STATES completed successfully 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.564: 91404090: ../libfprint/drivers/aes2501.c:547 145s (process:2931): libfprint-aes2501-DEBUG: 05:37:50.564: 91404097: ../libfprint/drivers/aes2501.c:820 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.564: Image device deactivation completed 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.564: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 145s (process:2931): libfprint-image-DEBUG: 05:37:50.566: Minutiae scan completed in 0.005644 secs 145s (process:2931): libfprint-device-DEBUG: 05:37:50.566: Device reported capture completion 145s (process:2931): libfprint-device-DEBUG: 05:37:50.566: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 145s (process:2931): libfprint-device-DEBUG: 05:37:50.566: Updated temperature model after 2.38 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 145s (process:2931): libfprint-image_device-DEBUG: 05:37:50.569: Image device close completed 145s (process:2931): libfprint-device-DEBUG: 05:37:50.569: Device reported close completion 145s (process:2931): libfprint-device-DEBUG: 05:37:50.569: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 145s (process:2931): libfprint-device-DEBUG: 05:37:50.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 145s ** (umockdev-run:2927): DEBUG: 05:37:50.648: umockdev.vala:154: Removing test bed /tmp/umockdev.WRK912 145s (umockdev-run:2927): GLib-DEBUG: 05:37:50.657: unsetenv() is not thread-safe and should not be used after threads are created 145s Comparing PNGs /tmp/libfprint-umockdev-test-4ca3qqmb/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 145s PASS: libfprint-2/driver-aes2501.test 145s Running test: libfprint-2/fp-context.test 145s TAP version 14 145s # random seed: R02Sd2b32a4d3d1e88a6d9b93f742598c33e 145s 1..9 145s # Start of context tests 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s ok 1 /context/new 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 145s ok 2 /context/no-devices 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 145s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-OC3412/virtual_image.socket 145s # libfprint-context-DEBUG: created 145s # libfprint-device-DEBUG: Device reported probe completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 145s ok 3 /context/has-virtual-device 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 145s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4AO412/virtual_image.socket 145s # libfprint-context-DEBUG: created 145s # libfprint-device-DEBUG: Device reported probe completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 145s ok 4 /context/enumerates-new-devices 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 145s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Z20212/virtual_image.socket 145s # libfprint-context-DEBUG: created 145s # libfprint-device-DEBUG: Device reported probe completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 145s ok 5 /context/remove-device-closed 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 145s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-NGU212/virtual_image.socket 145s # libfprint-context-DEBUG: created 145s # libfprint-device-DEBUG: Device reported probe completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:50.735: 91575329: ../libfprint/drivers/virtual-image.c:216 145s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_device_connection-DEBUG: 05:37:50.736: 91575508: ../libfprint/drivers/virtual-device-listener.c:153 145s # libfprint-image_device-DEBUG: Image device open completed 145s # libfprint-device-DEBUG: Device reported open completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:50.836: 91676310: ../libfprint/drivers/virtual-image.c:244 145s # libfprint-image_device-DEBUG: Image device close completed 145s # libfprint-device-DEBUG: Device reported close completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 145s ok 6 /context/remove-device-closing 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 145s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 145s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 145s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2NS912/virtual_image.socket 145s # libfprint-context-DEBUG: created 145s # libfprint-device-DEBUG: Device reported probe completion 145s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 145s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 145s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:50.947: 91787434: ../libfprint/drivers/virtual-image.c:216 145s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_device_connection-DEBUG: 05:37:50.948: 91787533: ../libfprint/drivers/virtual-device-listener.c:153 146s # libfprint-image_device-DEBUG: Image device open completed 146s # libfprint-device-DEBUG: Device reported open completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:51.049: 91888594: ../libfprint/drivers/virtual-image.c:244 146s # libfprint-image_device-DEBUG: Image device close completed 146s # libfprint-device-DEBUG: Device reported close completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 146s ok 7 /context/remove-device-open 146s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 146s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 146s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 146s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 146s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 146s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 146s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 146s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ACEF22/virtual_image.socket 146s # libfprint-context-DEBUG: created 146s # libfprint-device-DEBUG: Device reported probe completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:51.160: 92000377: ../libfprint/drivers/virtual-image.c:216 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_device_connection-DEBUG: 05:37:51.160: 92000440: ../libfprint/drivers/virtual-device-listener.c:153 146s # libfprint-image_device-DEBUG: Image device open completed 146s # libfprint-device-DEBUG: Device reported open completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:51.262: 92101521: ../libfprint/drivers/virtual-image.c:244 146s # libfprint-image_device-DEBUG: Image device close completed 146s # libfprint-device-DEBUG: Device reported close completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 146s ok 8 /context/remove-device-opening 146s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 146s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 146s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 146s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 146s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 146s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 146s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 146s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MNTH22/virtual_image.socket 146s # libfprint-context-DEBUG: created 146s # libfprint-device-DEBUG: Device reported probe completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:51.370: 92210362: ../libfprint/drivers/virtual-image.c:216 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_device_connection-DEBUG: 05:37:51.370: 92210437: ../libfprint/drivers/virtual-device-listener.c:153 146s # libfprint-image_device-DEBUG: Image device open completed 146s # libfprint-device-DEBUG: Device reported open completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s # libfprint-image_device-DEBUG: Activating image device 146s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 146s # libfprint-image_device-DEBUG: Image device activation completed 146s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 146s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 146s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s # libfprint-image_device-DEBUG: Deactivating image device 146s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 146s # libfprint-image_device-DEBUG: Image device deactivation completed 146s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 146s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 146s # libfprint-device-DEBUG: Device reported enroll completion 146s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2938): libfprint-virtual_image-DEBUG: 05:37:51.472: 92311817: ../libfprint/drivers/virtual-image.c:244 146s # libfprint-image_device-DEBUG: Image device close completed 146s # libfprint-device-DEBUG: Device reported close completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 146s ok 9 /context/remove-device-active 146s # End of context tests 146s PASS: libfprint-2/fp-context.test 146s Running test: libfprint-2/driver-fpcmoc.test 146s ** (umockdev-run:2962): DEBUG: 05:37:51.633: umockdev.vala:127: Created udev test bed /tmp/umockdev.GKS012 146s ** (umockdev-run:2962): DEBUG: 05:37:51.633: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 146s ** (umockdev-run:2962): DEBUG: 05:37:51.635: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 146s ** (umockdev-run:2962): DEBUG: 05:37:51.638: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.GKS012/dev/bus/usb/001/019 146s ** (umockdev-run:2962): DEBUG: 05:37:51.639: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 146s ** (umockdev-run:2962): DEBUG: 05:37:51.640: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 146s ** (umockdev-run:2962): DEBUG: 05:37:51.643: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.GKS012/dev/bus/usb/001/001 146s ** (umockdev-run:2962): DEBUG: 05:37:51.643: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 146s ** (umockdev-run:2962): DEBUG: 05:37:51.644: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 146s (process:2966): libfprint-context-DEBUG: 05:37:51.748: Initializing FpContext (libfprint version 1.94.9+tod1) 146s (process:2966): libfprint-tod-DEBUG: 05:37:51.748: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 146s (process:2966): libfprint-DEBUG: 05:37:51.750: fpi_device_fpcmoc_init enter --> 146s (process:2966): libfprint-DEBUG: 05:37:51.750: 92590270: ../libfprint/drivers/fpcmoc/fpc.c:1875 146s (process:2966): libfprint-context-DEBUG: 05:37:51.751: No driver found for USB device 1D6B:0002 146s (process:2966): libfprint-DEBUG: 05:37:51.751: fpc_dev_probe enter --> 146s (process:2966): libfprint-DEBUG: 05:37:51.754: Device name: FPC L:0001 FW:127010 146s (process:2966): libfprint-device-DEBUG: 05:37:51.755: Device reported probe completion 146s (process:2966): libfprint-device-DEBUG: 05:37:51.755: Completing action FPI_DEVICE_ACTION_PROBE in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.755: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.756: fpc_dev_open enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.756: [fpcmoc] FP_INIT_NUM_STATES entering state 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.757: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.757: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-DEBUG: 05:37:51.757: fpc_cmd_receive_cb current ssm request: 1 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.758: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.758: fpc_cmd_receive_cb current ssm request: 1 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.758: fpc_cmd_receive_cb recv evt data length: 38 146s (process:2966): libfprint-DEBUG: 05:37:51.758: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 146s (process:2966): libfprint-DEBUG: 05:37:51.759: fpc_evt_cb INIT: FW version: 1.27.0.10 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.759: [fpcmoc] FP_INIT_NUM_STATES entering state 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.759: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.759: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.759: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.760: fpc_cmd_receive_cb current ssm request: 96 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.760: fpc_init_load_db_cb got dbid size: 16 146s (process:2966): libfprint-DEBUG: 05:37:51.760: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.760: [fpcmoc] FP_INIT_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.760: Device reported open completion 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.760: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.760: Completing action FPI_DEVICE_ACTION_OPEN in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.760: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.760: fpc_dev_clear_storage enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.760: [fpcmoc] Clear storage entering state 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.760: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.760: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.761: fpc_cmd_receive_cb current ssm request: 98 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.761: [fpcmoc] Clear storage entering state 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.761: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.761: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.761: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.761: fpc_cmd_receive_cb current ssm request: 96 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.761: [fpcmoc] Clear storage completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.761: Clear Storage complete! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.762: Device reported deletion completion 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.762: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.762: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.762: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.762: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.762: fpc_dev_enroll enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.762: [fpcmoc] enroll entering state 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.762: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.762: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-DEBUG: 05:37:51.763: fpc_cmd_receive_cb current ssm request: 112 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.763: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.764: fpc_cmd_receive_cb current ssm request: 112 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.764: fpc_cmd_receive_cb recv evt data length: 790 146s (process:2966): libfprint-DEBUG: 05:37:51.764: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.765: [fpcmoc] enroll entering state 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.765: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.765: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.765: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.766: fpc_cmd_receive_cb current ssm request: 103 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.766: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-device-DEBUG: 05:37:51.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.766: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.766: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.766: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.767: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.767: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.768: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.768: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.768: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.768: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.768: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.768: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.768: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.769: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.769: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.769: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.769: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.769: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.769: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.769: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.769: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.769: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.770: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.770: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.770: Enrol Update status: 1, remaining: 11 146s (process:2966): libfprint-device-DEBUG: 05:37:51.770: Device reported enroll progress, reported 1 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.770: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.770: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.770: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.771: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.771: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.771: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.772: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.772: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.772: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.772: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.772: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.772: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.773: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.773: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.773: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.774: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.774: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.774: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.774: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.774: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.774: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.774: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.774: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.775: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.775: Enrol Update status: 1, remaining: 10 146s (process:2966): libfprint-device-DEBUG: 05:37:51.775: Device reported enroll progress, reported 2 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.775: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.775: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.775: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.775: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.776: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.776: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.777: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.777: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.777: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.777: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.777: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.777: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.777: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.777: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.777: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.777: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.778: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.778: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.778: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.778: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.778: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.778: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.779: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.779: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.779: Enrol Update status: 1, remaining: 9 146s (process:2966): libfprint-device-DEBUG: 05:37:51.779: Device reported enroll progress, reported 3 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.779: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.779: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.779: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.779: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.780: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.780: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.781: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.781: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.781: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.781: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.781: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.781: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.781: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.782: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.782: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.782: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.782: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.782: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.782: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.782: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.782: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.783: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.783: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.783: Enrol Update status: 1, remaining: 8 146s (process:2966): libfprint-device-DEBUG: 05:37:51.783: Device reported enroll progress, reported 4 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.783: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.783: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.783: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.784: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.784: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.784: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.785: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.785: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.785: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.785: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.785: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.785: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.786: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.786: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.786: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.787: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.787: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.787: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.787: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.787: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.787: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.787: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.787: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.788: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.788: Enrol Update status: 1, remaining: 7 146s (process:2966): libfprint-device-DEBUG: 05:37:51.788: Device reported enroll progress, reported 5 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.788: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.788: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.788: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.788: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.789: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.789: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.790: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.790: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.790: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.790: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.790: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.790: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.790: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.790: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.790: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.790: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.791: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.791: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.791: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.791: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.791: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.791: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.792: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.792: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.792: Enrol Update status: 5, remaining: 7 146s (process:2966): libfprint-DEBUG: 05:37:51.792: Sample overlapping ratio is too High 146s (process:2966): libfprint-device-DEBUG: 05:37:51.792: Device reported enroll progress, reported 5 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.792: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.792: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.792: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.793: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.793: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.793: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.794: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.794: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.794: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.794: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.794: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.794: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.794: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.794: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.794: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.794: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.795: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.795: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.795: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.795: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.795: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.795: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.796: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.796: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.796: Enrol Update status: 1, remaining: 6 146s (process:2966): libfprint-device-DEBUG: 05:37:51.796: Device reported enroll progress, reported 6 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.796: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.796: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.796: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.797: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.797: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.797: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.798: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.798: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.798: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.798: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.798: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.798: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.800: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.801: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.801: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.801: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.801: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.801: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.801: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.801: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.801: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.802: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.802: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.802: Enrol Update status: 1, remaining: 5 146s (process:2966): libfprint-device-DEBUG: 05:37:51.802: Device reported enroll progress, reported 7 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.802: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.802: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.802: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.802: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.803: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.803: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.804: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.804: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.804: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.804: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.804: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.804: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.804: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.804: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.804: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.804: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.805: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.805: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.805: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.805: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.805: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.805: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.805: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.806: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.806: Enrol Update status: 5, remaining: 5 146s (process:2966): libfprint-DEBUG: 05:37:51.806: Sample overlapping ratio is too High 146s (process:2966): libfprint-device-DEBUG: 05:37:51.806: Device reported enroll progress, reported 7 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.806: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.806: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.806: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.806: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.807: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.807: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.807: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.807: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.808: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.808: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.808: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.808: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.808: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.808: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.808: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.809: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.809: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.809: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.809: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.809: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.809: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.810: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.810: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.810: Enrol Update status: 1, remaining: 4 146s (process:2966): libfprint-device-DEBUG: 05:37:51.810: Device reported enroll progress, reported 8 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.810: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.810: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.810: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.810: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.811: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.811: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.812: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.812: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.812: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.812: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.812: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.812: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.812: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.812: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.812: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.812: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.813: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.813: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.813: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.813: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.813: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.813: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.814: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.814: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.814: Enrol Update status: 1, remaining: 3 146s (process:2966): libfprint-device-DEBUG: 05:37:51.814: Device reported enroll progress, reported 9 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.814: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.814: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.814: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.814: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.815: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.815: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.816: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.816: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.816: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.816: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.816: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.816: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.816: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.816: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.816: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.816: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.817: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.817: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.817: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.817: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.817: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.817: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.818: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.818: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.818: Enrol Update status: 1, remaining: 2 146s (process:2966): libfprint-device-DEBUG: 05:37:51.818: Device reported enroll progress, reported 10 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.818: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.818: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.818: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.818: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.819: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.819: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.819: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.819: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.819: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.819: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.819: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.819: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.820: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.820: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.820: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.821: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.821: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.821: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.821: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.821: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.821: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.821: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.821: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.821: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.821: Enrol Update status: 5, remaining: 2 146s (process:2966): libfprint-DEBUG: 05:37:51.821: Sample overlapping ratio is too High 146s (process:2966): libfprint-device-DEBUG: 05:37:51.821: Device reported enroll progress, reported 10 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.822: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.822: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.822: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.822: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.822: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.822: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.823: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.823: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.823: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.823: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.823: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.823: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.823: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.823: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.824: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.824: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.824: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.824: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.824: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.824: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.824: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.824: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.824: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.825: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.825: Enrol Update status: 1, remaining: 1 146s (process:2966): libfprint-device-DEBUG: 05:37:51.825: Device reported enroll progress, reported 11 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.825: [fpcmoc] enroll entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.825: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.825: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.825: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.825: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.826: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.826: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.826: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.826: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.826: [fpcmoc] enroll entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.826: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.826: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.827: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.827: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.827: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.828: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.828: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.828: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.828: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.828: [fpcmoc] enroll entering state 4 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.828: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.828: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.828: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.828: fpc_cmd_receive_cb current ssm request: 104 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.828: Enrol Update status: 0, remaining: 0 146s (process:2966): libfprint-device-DEBUG: 05:37:51.828: Device reported enroll progress, reported 12 of 25 have been completed 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.829: [fpcmoc] enroll entering state 5 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.829: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.829: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.829: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.829: fpc_cmd_receive_cb current ssm request: 105 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.829: Enrol End status: 0, fid: 0x0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.829: [fpcmoc] enroll entering state 6 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.829: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.829: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.830: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.830: fpc_cmd_receive_cb current ssm request: 107 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.830: [fpcmoc] enroll entering state 7 146s (process:2966): libfprint-DEBUG: 05:37:51.830: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.830: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.830: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.831: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.831: fpc_cmd_receive_cb current ssm request: 106 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.831: [fpcmoc] enroll entering state 8 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.831: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.831: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.832: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.832: fpc_cmd_receive_cb current ssm request: 97 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.832: [fpcmoc] enroll entering state 9 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.832: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.832: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.832: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.833: fpc_cmd_receive_cb current ssm request: 3 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.833: fpc_do_abort_cb Do abort for reasons 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.833: [fpcmoc] enroll entering state 10 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.833: [fpcmoc] enroll completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.833: Enrollment complete! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.833: Device reported enroll completion 146s (process:2966): libfprint-device-DEBUG: 05:37:51.833: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2966): libfprint-device-DEBUG: 05:37:51.833: Print for finger FP_FINGER_UNKNOWN enrolled 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.833: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.833: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.833: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.833: fpc_dev_template_list enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.833: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.833: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-DEBUG: 05:37:51.834: fpc_cmd_receive_cb current ssm request: 112 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.834: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.834: fpc_cmd_receive_cb current ssm request: 112 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.835: fpc_cmd_receive_cb recv evt data length: 790 146s (process:2966): libfprint-DEBUG: 05:37:51.835: Query templates complete! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.835: Device reported listing completion 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.835: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.835: Completing action FPI_DEVICE_ACTION_LIST in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.835: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.835: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.835: fpc_dev_verify_identify enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.835: [fpcmoc] verify_identify entering state 0 146s (process:2966): libfprint-device-DEBUG: 05:37:51.835: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.835: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.835: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-DEBUG: 05:37:51.836: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.836: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.836: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.836: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.837: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.837: [fpcmoc] verify_identify entering state 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.837: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.837: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.837: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.837: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.837: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.838: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.838: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.838: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.838: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.838: [fpcmoc] verify_identify entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.838: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.838: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.839: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.839: fpc_cmd_receive_cb current ssm request: 107 state: 0 146s (process:2966): libfprint-device-DEBUG: 05:37:51.839: Device reported verify result 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.839: [fpcmoc] verify_identify entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.839: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.839: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.839: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.840: fpc_cmd_receive_cb current ssm request: 3 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.840: fpc_do_abort_cb Do abort for reasons 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.840: [fpcmoc] verify_identify completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.840: Verify_identify complete! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.840: Device reported verify completion 146s (process:2966): libfprint-device-DEBUG: 05:37:51.840: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.840: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.840: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.840: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.840: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.840: fpc_dev_verify_identify enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.840: [fpcmoc] verify_identify entering state 0 146s (process:2966): libfprint-device-DEBUG: 05:37:51.840: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.840: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.840: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 146s (process:2966): libfprint-DEBUG: 05:37:51.842: fpc_cmd_receive_cb current ssm request: 2 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.842: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.844: fpc_cmd_receive_cb current ssm request: 2 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.844: fpc_cmd_receive_cb recv evt data length: 12 146s (process:2966): libfprint-DEBUG: 05:37:51.844: fpc_evt_cb Got finger down event (0) 146s (process:2966): libfprint-device-DEBUG: 05:37:51.844: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.844: [fpcmoc] verify_identify entering state 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.844: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.844: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.844: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.845: fpc_cmd_receive_cb current ssm request: 9 state: 0 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.845: [fpcmoc] FP_CMD_NUM_STATES entering state 1 146s (process:2966): libfprint-DEBUG: 05:37:51.847: fpc_cmd_receive_cb current ssm request: 9 state: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.847: fpc_cmd_receive_cb recv evt data length: 24 146s (process:2966): libfprint-DEBUG: 05:37:51.847: fpc_evt_cb Got capture event 146s (process:2966): libfprint-device-DEBUG: 05:37:51.847: Device reported finger status change: FP_FINGER_STATUS_NEEDED 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.847: [fpcmoc] verify_identify entering state 2 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.847: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.847: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.847: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.848: fpc_cmd_receive_cb current ssm request: 107 state: 0 146s (process:2966): libfprint-device-DEBUG: 05:37:51.848: Device reported identify result 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.848: [fpcmoc] verify_identify entering state 3 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.848: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.848: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.849: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.849: fpc_cmd_receive_cb current ssm request: 3 state: 0 146s (process:2966): libfprint-DEBUG: 05:37:51.849: fpc_do_abort_cb Do abort for reasons 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.849: [fpcmoc] verify_identify completed successfully 146s (process:2966): libfprint-DEBUG: 05:37:51.849: Verify_identify complete! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.849: Device reported identify completion 146s (process:2966): libfprint-device-DEBUG: 05:37:51.849: Device reported finger status change: FP_FINGER_STATUS_NONE 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.849: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.849: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.849: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.849: fpc_dev_template_delete enter --> 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.849: [fpcmoc] FP_CMD_NUM_STATES entering state 0 146s (process:2966): libfprint-DEBUG: 05:37:51.849: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 146s (process:2966): libfprint-DEBUG: 05:37:51.850: fpc_dev_template_delete exit <-- 146s (process:2966): libfprint-DEBUG: 05:37:51.851: fpc_cmd_receive_cb current ssm request: 99 state: 0 146s (process:2966): libfprint-device-DEBUG: 05:37:51.851: Device reported deletion completion 146s (process:2966): libfprint-SSM-DEBUG: 05:37:51.851: [fpcmoc] FP_CMD_NUM_STATES completed successfully 146s (process:2966): libfprint-device-DEBUG: 05:37:51.851: Completing action FPI_DEVICE_ACTION_DELETE in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.851: Not updating temperature model, device can run continuously! 146s (process:2966): libfprint-DEBUG: 05:37:51.851: fpc_dev_close enter --> 146s (process:2966): libfprint-device-DEBUG: 05:37:51.852: Device reported close completion 146s (process:2966): libfprint-device-DEBUG: 05:37:51.852: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 146s (process:2966): libfprint-device-DEBUG: 05:37:51.852: Not updating temperature model, device can run continuously! 146s Clear 146s Clear done 146s enrolling 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 1, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 2, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 3, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 4, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 5, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 6, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 7, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 8, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 9, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 10, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 11, None, None, None) 146s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x6ff206229f80 (FpiDeviceFpcMoc at 0x23e0bdd0)>, 12, None, None, None) 146s enroll done 146s listing 146s listing done 146s verifying 146s verify done 146s async identifying 146s indentification_done: 146s deleting 146s delete done 146s ** (umockdev-run:2962): DEBUG: 05:37:51.875: umockdev.vala:154: Removing test bed /tmp/umockdev.GKS012 146s (umockdev-run:2962): GLib-DEBUG: 05:37:51.882: unsetenv() is not thread-safe and should not be used after threads are created 146s PASS: libfprint-2/driver-fpcmoc.test 146s Running test: libfprint-2/driver-elanmoc.test 146s ** (umockdev-run:2974): DEBUG: 05:37:51.939: umockdev.vala:127: Created udev test bed /tmp/umockdev.KOS912 146s ** (umockdev-run:2974): DEBUG: 05:37:51.939: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 146s ** (umockdev-run:2974): DEBUG: 05:37:51.944: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 146s ** (umockdev-run:2974): DEBUG: 05:37:51.951: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KOS912/dev/bus/usb/001/003 146s ** (umockdev-run:2974): DEBUG: 05:37:51.951: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 146s ** (umockdev-run:2974): DEBUG: 05:37:51.954: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 146s ** (umockdev-run:2974): DEBUG: 05:37:51.959: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KOS912/dev/bus/usb/001/001 146s ** (umockdev-run:2974): DEBUG: 05:37:51.959: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 146s ** (umockdev-run:2974): DEBUG: 05:37:51.961: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 147s (process:2978): libfprint-context-DEBUG: 05:37:52.060: Initializing FpContext (libfprint version 1.94.9+tod1) 147s (process:2978): libfprint-tod-DEBUG: 05:37:52.060: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.062: 92902351: ../libfprint/drivers/elanmoc/elanmoc.c:1154 147s (process:2978): libfprint-context-DEBUG: 05:37:52.063: No driver found for USB device 1D6B:0002 147s (process:2978): libfprint-device-DEBUG: 05:37:52.063: Device reported probe completion 147s (process:2978): libfprint-device-DEBUG: 05:37:52.063: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.063: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.065: [elanmoc] DEV_INIT_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.065: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.066: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.068: [elanmoc] DEV_INIT_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.068: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.070: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.070: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.071: [elanmoc] DEV_INIT_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.071: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.071: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.072: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.073: elanmoc FW Version 8004 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.073: [elanmoc] DEV_INIT_STATES entering state 3 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.073: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.073: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.074: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.075: elanmoc last_read DIM 0x57(87) 0x6B(107) 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.075: [elanmoc] DEV_INIT_STATES entering state 4 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.075: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.075: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.076: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.077: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.077: [elanmoc] DEV_INIT_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.077: Device reported open completion 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.077: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.077: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.077: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.078: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.078: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.078: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.079: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.080: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.080: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.080: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.080: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.081: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.082: ##### Re-Enrollment Case! ##### 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.082: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.082: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.082: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.082: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.083: Device reported enroll progress, reported 1 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.083: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.084: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.084: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.085: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.086: Device reported enroll progress, reported 2 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.086: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.086: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.086: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.087: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.088: Device reported enroll progress, reported 3 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.088: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.088: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.088: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.089: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.090: Device reported enroll progress, reported 4 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.090: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.090: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.090: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.091: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.092: Device reported enroll progress, reported 5 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.092: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.092: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.092: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.093: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.094: Device reported enroll progress, reported 6 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.094: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.094: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.094: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.095: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.096: Device reported enroll progress, reported 7 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.096: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.096: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.096: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.097: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.098: Device reported enroll progress, reported 7 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.098: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.098: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.098: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.099: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.100: Device reported enroll progress, reported 8 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.100: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.100: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.100: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.101: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.102: Device reported enroll progress, reported 8 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.102: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.102: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.102: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.102: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.104: Device reported enroll progress, reported 9 of 9 have been completed 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.104: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.104: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.104: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.104: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.105: elanmoc_commit_cb success 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.105: Enrollment was successful! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.105: Device reported enroll completion 147s (process:2978): libfprint-device-DEBUG: 05:37:52.105: Print for finger FP_FINGER_UNKNOWN enrolled 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.105: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.105: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.105: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.105: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.105: [elanmoc] MOC_LIST_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.105: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.106: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.107: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.107: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.107: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.108: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.108: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.109: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.109: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.109: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.110: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.111: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.111: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.111: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.112: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.113: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.113: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.114: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.115: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.116: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.116: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.116: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.117: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.117: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.117: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.118: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.118: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.119: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.119: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.120: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.120: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.121: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.121: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.121: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.122: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.122: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.122: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.123: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.123: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.124: [elanmoc] MOC_LIST_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.124: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.125: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.125: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.126: Device reported listing completion 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.126: [elanmoc] MOC_LIST_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.126: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.126: Completing action FPI_DEVICE_ACTION_LIST in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.126: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.127: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.127: [elanmoc] IDENTIFY_NUM_STATES entering state 0 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.127: elanmoc elan_identify_run_state 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.127: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.127: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.127: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.128: [elanmoc] IDENTIFY_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.128: elanmoc elan_identify_run_state 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.128: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.128: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.129: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.129: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.130: Verify was successful! for user: 0 mesg_code: 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.131: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.131: [elanmoc] IDENTIFY_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.131: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.131: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.132: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 147s (process:2978): libfprint-device-DEBUG: 05:37:52.132: Device reported verify result 147s (process:2978): libfprint-device-DEBUG: 05:37:52.132: Device reported verify completion 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.132: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.133: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.133: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.133: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.133: [elanmoc] IDENTIFY_NUM_STATES entering state 0 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.133: elanmoc elan_identify_run_state 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.133: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.133: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.134: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.135: [elanmoc] IDENTIFY_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.135: elanmoc elan_identify_run_state 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.135: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.135: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.136: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.136: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.137: Verify was successful! for user: 0 mesg_code: 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.137: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.137: [elanmoc] IDENTIFY_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.137: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.138: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.139: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 147s (process:2978): libfprint-device-DEBUG: 05:37:52.139: Device reported identify result 147s (process:2978): libfprint-device-DEBUG: 05:37:52.139: Device reported identify completion 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.139: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.139: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.139: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.139: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.139: [elanmoc] DELETE_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.139: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.140: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-device-DEBUG: 05:37:52.143: Device reported deletion completion 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.143: [elanmoc] DELETE_NUM_STATES completed successfully 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.143: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.143: Completing action FPI_DEVICE_ACTION_DELETE in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.144: Not updating temperature model, device can run continuously! 147s (process:2978): libfprint-elanmoc-DEBUG: 05:37:52.144: Elanmoc dev_exit 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.144: [elanmoc] DEV_EXIT_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.144: [elanmoc] FP_CMD_NUM_STATES entering state 0 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.145: [elanmoc] FP_CMD_NUM_STATES entering state 1 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.145: [elanmoc] DEV_EXIT_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.145: Device reported close completion 147s (process:2978): libfprint-SSM-DEBUG: 05:37:52.146: [elanmoc] FP_CMD_NUM_STATES completed successfully 147s (process:2978): libfprint-device-DEBUG: 05:37:52.146: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s (process:2978): libfprint-device-DEBUG: 05:37:52.146: Not updating temperature model, device can run continuously! 147s enrolling 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 1, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 2, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 3, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 4, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 5, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 6, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 7, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 8, None, None, None) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 147s finger status: 147s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x6afb97829e80 (FpiDeviceElanmoc at 0x387067e0)>, 9, None, None, None) 147s enroll done 147s listing 147s listing done 147s verifying 147s verify done 147s async identifying 147s indentification_done: 147s deleting 147s delete done 147s ** (umockdev-run:2974): DEBUG: 05:37:52.160: umockdev.vala:154: Removing test bed /tmp/umockdev.KOS912 147s (umockdev-run:2974): GLib-DEBUG: 05:37:52.170: unsetenv() is not thread-safe and should not be used after threads are created 147s PASS: libfprint-2/driver-elanmoc.test 147s Running test: libfprint-2/driver-focaltech_moc.test 147s ** (umockdev-run:2986): DEBUG: 05:37:52.221: umockdev.vala:127: Created udev test bed /tmp/umockdev.Q91D22 147s ** (umockdev-run:2986): DEBUG: 05:37:52.222: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 147s ** (umockdev-run:2986): DEBUG: 05:37:52.231: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 147s ** (umockdev-run:2986): DEBUG: 05:37:52.237: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Q91D22/dev/bus/usb/003/006 147s ** (umockdev-run:2986): DEBUG: 05:37:52.237: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 147s ** (umockdev-run:2986): DEBUG: 05:37:52.249: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 147s ** (umockdev-run:2986): DEBUG: 05:37:52.254: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Q91D22/dev/bus/usb/003/002 147s ** (umockdev-run:2986): DEBUG: 05:37:52.255: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 147s ** (umockdev-run:2986): DEBUG: 05:37:52.266: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 147s ** (umockdev-run:2986): DEBUG: 05:37:52.270: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Q91D22/dev/bus/usb/003/001 147s ** (umockdev-run:2986): DEBUG: 05:37:52.270: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 147s ** (umockdev-run:2986): DEBUG: 05:37:52.273: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 147s ** (umockdev-run:2986): DEBUG: 05:37:52.277: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 147s ** (umockdev-run:2986): DEBUG: 05:37:52.278: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 147s (process:2990): libfprint-context-DEBUG: 05:37:52.398: Initializing FpContext (libfprint version 1.94.9+tod1) 147s (process:2990): libfprint-tod-DEBUG: 05:37:52.399: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.403: 93242647: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1852 147s (process:2990): libfprint-context-DEBUG: 05:37:52.403: No driver found for USB device 05E3:0608 147s (process:2990): libfprint-context-DEBUG: 05:37:52.403: No driver found for USB device 1D6B:0002 147s (process:2990): libfprint-device-DEBUG: 05:37:52.403: Device reported probe completion 147s (process:2990): libfprint-device-DEBUG: 05:37:52.403: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s (process:2990): libfprint-device-DEBUG: 05:37:52.403: Not updating temperature model, device can run continuously! 147s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 147s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.405: class:dc, subclass:a0, protocol:b0 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.405: bytes size:0 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.405: 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 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.405: bytes size:0 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.405: 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 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.406: [focaltech_moc] DEV_INIT_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.406: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.406: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.407: focaltechmoc enroll_times: 10 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.407: [focaltech_moc] DEV_INIT_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.407: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.408: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.408: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.409: [focaltech_moc] DEV_INIT_STATES completed successfully 147s (process:2990): libfprint-device-DEBUG: 05:37:52.409: Device reported open completion 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.409: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-device-DEBUG: 05:37:52.409: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s (process:2990): libfprint-device-DEBUG: 05:37:52.409: Not updating temperature model, device can run continuously! 147s (process:2990): libfprint-device-DEBUG: 05:37:52.409: Not updating temperature model, device can run continuously! 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.409: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.409: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.410: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.411: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.411: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.411: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.412: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.412: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.412: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.413: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.413: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.414: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.414: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.415: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.415: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.416: focaltechmoc user id: FP1-00000000-0-00000000-nobody 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.416: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.416: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.416: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.416: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.417: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.417: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.467: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.467: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.468: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.469: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.469: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.519: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.519: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.520: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.521: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.521: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.571: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.571: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.575: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.576: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.576: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.626: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.626: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.631: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.632: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.632: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.682: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.682: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.683: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.685: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.685: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.735: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.735: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.736: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.737: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.737: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.738: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.738: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-device-DEBUG: 05:37:52.739: Device reported enroll progress, reported 1 of 10 have been completed 147s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:52.739: focaltechmoc remain: 9 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.739: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.739: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.740: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.741: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.742: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.742: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.792: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.792: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.794: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.794: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.844: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.844: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.845: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.847: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.847: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.897: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.897: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.898: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.899: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.899: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.949: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.949: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.950: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.951: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 147s (process:2990): libfprint-SSM-DEBUG: 05:37:52.951: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.001: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.001: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.002: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.003: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.003: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.004: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.005: Device reported enroll progress, reported 2 of 10 have been completed 148s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:53.005: focaltechmoc remain: 8 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.005: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.005: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.006: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.006: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.007: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.007: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.057: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.057: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.058: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.059: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.059: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.060: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.060: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.061: Device reported enroll progress, reported 3 of 10 have been completed 148s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:53.061: focaltechmoc remain: 7 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.061: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.061: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.062: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.062: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.064: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.064: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.114: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.114: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.115: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.116: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.116: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s Executing: libfprint-2/driver-focaltech_moc.test 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.167: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.167: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.167: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.168: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.168: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.218: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.219: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.220: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.220: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.271: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.271: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.272: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.272: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.272: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.322: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.322: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.324: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.324: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.324: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.326: Device reported enroll progress, reported 4 of 10 have been completed 148s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:53.326: focaltechmoc remain: 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.326: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.326: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.326: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.327: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.327: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.328: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.378: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.379: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.380: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.380: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.380: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.431: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.431: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.432: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.432: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.433: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.483: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.483: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.484: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.484: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.484: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.487: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.487: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.488: Device reported enroll progress, reported 5 of 10 have been completed 148s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:53.488: focaltechmoc remain: 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.488: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.488: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.491: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.491: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.492: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.492: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.542: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.542: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.542: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.543: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.543: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.593: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.593: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.594: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.595: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.595: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.645: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.645: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.646: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.647: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.647: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.697: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.697: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.698: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.699: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.699: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.699: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.700: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.700: Device reported enroll progress, reported 6 of 10 have been completed 148s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:53.700: focaltechmoc remain: 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.700: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.700: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.701: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.701: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.702: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.702: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.702: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.702: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.707: Device reported enroll progress, reported 6 of 10 have been completed 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.707: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.707: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.707: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.708: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.711: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.711: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.761: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.761: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.762: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.767: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.767: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.817: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.817: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.818: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.818: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.818: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.868: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.868: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.869: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.870: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.870: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.920: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.920: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.921: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.921: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.921: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.922: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.922: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-device-DEBUG: 05:37:53.923: Device reported enroll progress, reported 7 of 10 have been completed 148s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:53.923: focaltechmoc remain: 3 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.923: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.923: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.923: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.923: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.924: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 148s (process:2990): libfprint-SSM-DEBUG: 05:37:53.924: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:53.974: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:53.974: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:53.975: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:53.976: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 149s (process:2990): libfprint-SSM-DEBUG: 05:37:53.976: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.026: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.026: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.027: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.027: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.027: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.028: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.028: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-device-DEBUG: 05:37:54.029: Device reported enroll progress, reported 8 of 10 have been completed 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.029: focaltechmoc remain: 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.029: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.029: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.029: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.030: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.030: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.030: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.080: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.080: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.081: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.082: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.082: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.082: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.082: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-device-DEBUG: 05:37:54.083: Device reported enroll progress, reported 9 of 10 have been completed 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.083: focaltechmoc remain: 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.083: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.083: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.084: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.084: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.085: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.085: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.135: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.135: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.136: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.136: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.136: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.136: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.137: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-device-DEBUG: 05:37:54.137: Device reported enroll progress, reported 10 of 10 have been completed 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.137: focaltechmoc remain: 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.137: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.137: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.138: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.138: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.139: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.139: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.139: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.139: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.140: focaltech_moc_commit_cb success 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.140: Enrollment was successful! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.140: Device reported enroll completion 149s (process:2990): libfprint-device-DEBUG: 05:37:54.140: Print for finger FP_FINGER_UNKNOWN enrolled 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.140: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.140: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-device-DEBUG: 05:37:54.140: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.140: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.140: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.140: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.143: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.144: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.144: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.144: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.145: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.145: focaltechmoc add slot: 0 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.145: FP1-00000000-0-00000000-nobody 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.145: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 149s (process:2990): libfprint-device-DEBUG: 05:37:54.145: Device reported listing completion 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.145: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.145: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-device-DEBUG: 05:37:54.146: Completing action FPI_DEVICE_ACTION_LIST in idle! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.146: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.146: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.146: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.146: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.147: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.147: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.147: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.148: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.148: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.149: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.149: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.199: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.199: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.200: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.203: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.203: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.253: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.253: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.254: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.254: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.254: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.304: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.304: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.305: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.306: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.306: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.359: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.359: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.360: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.361: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.361: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.361: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.362: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.362: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.362: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.363: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.363: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-device-DEBUG: 05:37:54.364: Device reported verify result 149s (process:2990): libfprint-device-DEBUG: 05:37:54.364: Device reported verify completion 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.364: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.364: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-device-DEBUG: 05:37:54.364: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.364: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.364: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.364: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.364: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.365: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.366: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.366: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.366: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.366: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.367: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.367: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.417: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.417: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.418: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.420: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.420: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.470: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.470: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.471: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.472: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.472: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.472: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.472: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.473: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.473: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.474: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.474: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-device-DEBUG: 05:37:54.475: Device reported identify result 149s (process:2990): libfprint-device-DEBUG: 05:37:54.475: Device reported identify completion 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.475: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.475: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-device-DEBUG: 05:37:54.475: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.475: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.476: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.476: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.476: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.477: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.477: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.477: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.478: focaltechmoc add slot: 0 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.478: FP1-00000000-0-00000000-nobody 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.478: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.479: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.479: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.480: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.480: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.480: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.481: delete slot 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 149s (process:2990): libfprint-device-DEBUG: 05:37:54.481: Device reported deletion completion 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 149s (process:2990): libfprint-device-DEBUG: 05:37:54.481: Completing action FPI_DEVICE_ACTION_DELETE in idle! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.481: Not updating temperature model, device can run continuously! 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.481: Focaltechmoc dev_exit 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] DEV_EXIT_STATES entering state 0 149s (process:2990): libfprint-SSM-DEBUG: 05:37:54.481: [focaltech_moc] DEV_EXIT_STATES completed successfully 149s (process:2990): libfprint-focaltech_moc-DEBUG: 05:37:54.481: class:dc, subclass:a0, protocol:b0 149s (process:2990): libfprint-device-DEBUG: 05:37:54.483: Device reported close completion 149s (process:2990): libfprint-device-DEBUG: 05:37:54.483: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 149s (process:2990): libfprint-device-DEBUG: 05:37:54.483: Not updating temperature model, device can run continuously! 149s enrolling 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 1, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 2, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 3, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 4, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 5, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 6, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 7, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 8, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 9, None, None, None) 149s finger status: 149s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x75b031429e40 (FpiDeviceFocaltechMoc at 0x29199240)>, 10, None, None, None) 149s enroll done 149s listing 149s listing done 149s verifying 149s verify done 149s async identifying 149s indentification_done: 149s deleting 149s delete done 149s ** (umockdev-run:2986): DEBUG: 05:37:54.500: umockdev.vala:154: Removing test bed /tmp/umockdev.Q91D22 149s (umockdev-run:2986): GLib-DEBUG: 05:37:54.510: unsetenv() is not thread-safe and should not be used after threads are created 149s PASS: libfprint-2/driver-focaltech_moc.test 149s Running test: libfprint-2/driver-synaptics.test 149s ** (umockdev-run:2998): DEBUG: 05:37:54.559: umockdev.vala:127: Created udev test bed /tmp/umockdev.H0C212 149s ** (umockdev-run:2998): DEBUG: 05:37:54.559: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 149s ** (umockdev-run:2998): DEBUG: 05:37:54.560: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 149s ** (umockdev-run:2998): DEBUG: 05:37:54.563: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.H0C212/dev/bus/usb/001/004 149s ** (umockdev-run:2998): DEBUG: 05:37:54.563: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 149s ** (umockdev-run:2998): DEBUG: 05:37:54.564: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 149s ** (umockdev-run:2998): DEBUG: 05:37:54.567: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.H0C212/dev/bus/usb/001/001 149s ** (umockdev-run:2998): DEBUG: 05:37:54.567: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 149s ** (umockdev-run:2998): DEBUG: 05:37:54.567: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 149s (process:3002): libfprint-context-DEBUG: 05:37:54.659: Initializing FpContext (libfprint version 1.94.9+tod1) 149s (process:3002): libfprint-tod-DEBUG: 05:37:54.659: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 149s (process:3002): libfprint-context-DEBUG: 05:37:54.662: No driver found for USB device 1D6B:0002 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.662: 95501954: ../libfprint/drivers/synaptics/synaptics.c:1247 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.665: Build Time: 1596608839 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.665: Build Num: 3273255 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.665: Version: 10.1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.665: Target: 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.666: Product: 65 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.666: sequence number is 1 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.666: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.666: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.667: Device reported probe completion 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.667: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.667: Completing action FPI_DEVICE_ACTION_PROBE in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.667: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.669: 95508687: ../libfprint/drivers/synaptics/synaptics.c:1407 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.669: sequence number is 2 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.669: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.670: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.670: Device reported open completion 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.670: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.670: Completing action FPI_DEVICE_ACTION_OPEN in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.670: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.670: clear all prints in database 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.670: sequence number is 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.670: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.671: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.672: Deleting All Enrolled Users is 0% complete 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.672: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.673: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.673: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.673: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.673: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.673: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.674: Deleting All Enrolled Users is 100% complete 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.674: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.675: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.675: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.675: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.675: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.675: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.676: Successfully deleted all enrolled user 149s (process:3002): libfprint-device-DEBUG: 05:37:54.676: Device reported deletion completion 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.676: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.676: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.676: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.677: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.677: 95517053: ../libfprint/drivers/synaptics/synaptics.c:1018 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.677: user_id: FP1-00000000-0-00000000-nobody, finger: 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.677: sequence number is 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.677: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.678: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.678: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.679: Place Finger on the Sensor! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.679: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.679: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.679: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.680: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.680: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.680: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.681: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.681: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.681: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.682: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.682: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.683: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.683: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.683: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.683: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.684: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.684: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.684: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.685: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.685: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.685: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.686: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.686: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.686: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.686: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.687: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.687: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.688: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.688: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.688: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.688: Enrollment is 12 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.688: Device reported enroll progress, reported 1 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.688: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.689: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.689: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.690: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.690: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.690: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.690: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.690: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.690: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.690: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.691: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.691: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.692: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.692: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.693: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.693: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.693: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.693: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.693: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.694: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.694: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.694: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.695: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.695: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.695: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.695: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.695: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.696: Enrollment is 25 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.696: Device reported enroll progress, reported 2 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.696: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.697: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.697: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.697: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.697: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.697: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.698: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.698: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.698: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.699: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.699: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.699: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.699: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.699: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.700: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.700: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.703: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.703: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.704: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.704: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.704: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.705: Enrollment is 37 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.705: Device reported enroll progress, reported 3 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.705: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.705: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.706: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.706: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.706: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.706: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.707: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.707: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.707: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.707: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.707: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.707: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.708: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.708: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.708: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.709: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.709: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.709: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.709: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.709: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.709: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.710: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.710: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.710: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.711: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.711: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.711: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.711: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.712: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.712: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.712: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.713: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.713: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.713: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.713: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.713: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.714: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.714: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.714: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.714: Enrollment is 50 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.714: Device reported enroll progress, reported 4 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.714: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.715: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.715: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.716: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.716: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.716: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.716: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.716: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.716: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.717: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.717: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.717: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.717: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.717: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.718: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.718: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.719: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.719: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.719: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.719: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.719: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.720: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.720: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.720: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.720: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.720: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.721: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.721: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.721: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.722: Enrollment is 62 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.722: Device reported enroll progress, reported 5 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.722: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.722: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.722: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.723: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.723: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.723: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.724: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.724: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.724: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.724: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.724: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.725: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.725: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.725: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.725: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.725: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.726: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.726: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.727: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.727: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.727: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.727: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.727: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.727: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.728: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.728: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.729: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.729: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.729: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.729: Enrollment is 62 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.729: Device reported enroll progress, reported 5 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.729: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.730: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.731: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.731: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.731: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.732: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.732: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.732: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.732: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.732: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.733: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.733: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.734: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.734: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.734: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.734: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.734: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.735: Enrollment is 75 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.735: Device reported enroll progress, reported 6 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.735: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.736: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.736: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.736: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.736: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.736: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.737: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.737: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.737: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.737: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.738: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.738: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.738: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.738: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.738: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.739: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.739: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.739: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.739: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.739: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.740: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.740: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.740: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.740: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.741: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.741: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.741: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.741: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.742: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.742: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.742: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.743: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.743: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.743: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.743: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.743: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.744: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.744: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.744: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.745: Enrollment is 87 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.745: Device reported enroll progress, reported 7 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.745: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.746: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.746: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.746: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.746: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.746: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.747: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.747: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.747: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.748: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.748: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.748: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.748: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.748: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.749: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.749: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.750: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.750: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.750: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.750: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.750: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.751: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.751: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.751: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.752: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.752: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.752: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.752: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.752: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.753: Enrollment is 100 % 149s (process:3002): libfprint-device-DEBUG: 05:37:54.753: Device reported enroll progress, reported 8 of 8 have been completed 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.753: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.754: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.754: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.754: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.754: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.754: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.755: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.755: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.755: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.755: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.756: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.756: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.756: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.756: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.756: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.757: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.757: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.757: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.757: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.758: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.758: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.758: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.759: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.759: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.759: Enrollment was successful! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.759: Device reported enroll completion 149s (process:3002): libfprint-device-DEBUG: 05:37:54.759: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:3002): libfprint-device-DEBUG: 05:37:54.759: Print for finger FP_FINGER_UNKNOWN enrolled 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.759: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.759: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.759: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.760: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.760: data is 0x1a125f20 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.760: 95599584: ../libfprint/drivers/synaptics/synaptics.c:650 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.760: sequence number is 5 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.760: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.760: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.763: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.763: Place Finger on the Sensor! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.763: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.763: got suspend request 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.764: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.764: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.764: got resume request 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.764: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.764: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.765: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.765: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.766: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.766: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.766: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.767: Finger is now on the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.767: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.767: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.767: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.767: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.768: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.768: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.768: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.769: Fingerprint image capture complete! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.769: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.770: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.770: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.770: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.770: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.770: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-device-DEBUG: 05:37:54.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.771: Finger is now off the sensor 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.771: Received message with 0 sequence number 0x91, ignoring! 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.771: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.772: interrupt transfer done 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.772: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.773: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.773: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.773: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.774: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 149s (process:3002): libfprint-device-DEBUG: 05:37:54.774: Device reported verify result 149s (process:3002): libfprint-device-DEBUG: 05:37:54.774: Device reported verify completion 149s (process:3002): libfprint-device-DEBUG: 05:37:54.774: Device reported finger status change: FP_FINGER_STATUS_NONE 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.774: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.774: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.774: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.774: data is 0x1a125f20 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.774: 95613876: ../libfprint/drivers/synaptics/synaptics.c:1127 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.774: sequence number is 6 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.774: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.775: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s libusb: warning [libusb_exit] device 1.1 still referenced 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.776: Successfully deleted enrolled user 149s (process:3002): libfprint-device-DEBUG: 05:37:54.776: Device reported deletion completion 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.776: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.776: Completing action FPI_DEVICE_ACTION_DELETE in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.776: Not updating temperature model, device can run continuously! 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.776: 95616239: ../libfprint/drivers/synaptics/synaptics.c:1428 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.776: sequence number is 7 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.776: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.777: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 149s (process:3002): libfprint-synaptics-DEBUG: 05:37:54.779: Fingerprint sensor ready to be powered down 149s (process:3002): libfprint-device-DEBUG: 05:37:54.779: Device reported close completion 149s (process:3002): libfprint-SSM-DEBUG: 05:37:54.779: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 149s (process:3002): libfprint-device-DEBUG: 05:37:54.779: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 149s (process:3002): libfprint-device-DEBUG: 05:37:54.779: Not updating temperature model, device can run continuously! 149s enrolling 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 1, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 2, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 3, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 4, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 5, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 6, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 7, None, None, None) 149s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7abf3b189e00 (FpiDeviceSynaptics at 0x1a129d90)>, 8, None, None, None) 149s enroll done 149s verifying 149s verify done 149s deleting 149s delete done 149s ** (umockdev-run:2998): DEBUG: 05:37:54.792: umockdev.vala:154: Removing test bed /tmp/umockdev.H0C212 149s (umockdev-run:2998): GLib-DEBUG: 05:37:54.798: unsetenv() is not thread-safe and should not be used after threads are created 149s PASS: libfprint-2/driver-synaptics.test 149s Running test: libfprint-2/driver-upektc_img-tcs1s.test 149s ** (umockdev-run:3010): DEBUG: 05:37:54.853: umockdev.vala:127: Created udev test bed /tmp/umockdev.8JU512 149s ** (umockdev-run:3010): DEBUG: 05:37:54.853: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 149s ** (umockdev-run:3010): DEBUG: 05:37:54.857: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 149s ** (umockdev-run:3010): DEBUG: 05:37:54.860: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.8JU512/dev/bus/usb/003/004 149s ** (umockdev-run:3010): DEBUG: 05:37:54.861: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 149s ** (umockdev-run:3010): DEBUG: 05:37:54.864: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 149s ** (umockdev-run:3010): DEBUG: 05:37:54.867: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.8JU512/dev/bus/usb/003/001 149s ** (umockdev-run:3010): DEBUG: 05:37:54.867: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 149s ** (umockdev-run:3010): DEBUG: 05:37:54.869: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 149s ** (umockdev-run:3010): DEBUG: 05:37:54.872: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 149s ** (umockdev-run:3010): DEBUG: 05:37:54.873: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 149s (process:3014): libfprint-context-DEBUG: 05:37:54.964: Initializing FpContext (libfprint version 1.94.9+tod1) 149s (process:3014): libfprint-tod-DEBUG: 05:37:54.965: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 149s (process:3014): libfprint-context-DEBUG: 05:37:54.967: No driver found for USB device 1D6B:0002 149s (process:3014): libfprint-device-DEBUG: 05:37:54.967: Device reported probe completion 149s (process:3014): libfprint-device-DEBUG: 05:37:54.967: Completing action FPI_DEVICE_ACTION_PROBE in idle! 149s (process:3014): libfprint-device-DEBUG: 05:37:54.967: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 149s (process:3014): libfprint-image_device-DEBUG: 05:37:54.969: Image device open completed 149s (process:3014): libfprint-device-DEBUG: 05:37:54.969: Device reported open completion 149s (process:3014): libfprint-device-DEBUG: 05:37:54.969: Completing action FPI_DEVICE_ACTION_OPEN in idle! 149s (process:3014): libfprint-device-DEBUG: 05:37:54.969: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 149s (process:3014): libfprint-device-DEBUG: 05:37:54.969: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 149s (process:3014): libfprint-image_device-DEBUG: 05:37:54.969: Activating image device 149s (process:3014): libfprint-image_device-DEBUG: 05:37:54.969: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 149s (process:3014): libfprint-SSM-DEBUG: 05:37:54.969: [upektc_img] ACTIVATE_NUM_STATES entering state 0 149s (process:3014): libfprint-SSM-DEBUG: 05:37:54.970: [upektc_img] ACTIVATE_NUM_STATES entering state 1 149s (process:3014): libfprint-SSM-DEBUG: 05:37:54.970: [upektc_img] ACTIVATE_NUM_STATES entering state 2 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.971: [upektc_img] ACTIVATE_NUM_STATES entering state 3 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.972: [upektc_img] ACTIVATE_NUM_STATES entering state 4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.972: [upektc_img] ACTIVATE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.973: [upektc_img] ACTIVATE_NUM_STATES entering state 6 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.974: [upektc_img] ACTIVATE_NUM_STATES entering state 7 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.975: [upektc_img] ACTIVATE_NUM_STATES entering state 8 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.979: [upektc_img] ACTIVATE_NUM_STATES entering state 9 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.980: [upektc_img] ACTIVATE_NUM_STATES entering state 10 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.980: [upektc_img] ACTIVATE_NUM_STATES entering state 11 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.981: Sensor type : TCS1x, width x height: 256 x 360 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.981: [upektc_img] ACTIVATE_NUM_STATES completed successfully 150s (process:3014): libfprint-image_device-DEBUG: 05:37:54.981: Image device activation completed 150s (process:3014): libfprint-image_device-DEBUG: 05:37:54.981: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:3014): libfprint-image_device-DEBUG: 05:37:54.981: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 150s (process:3014): libfprint-device-DEBUG: 05:37:54.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.981: [upektc_img] CAPTURE_NUM_STATES entering state 0 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.982: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.982: request completed, len: 0000 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.982: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.983: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.983: 18th byte is 0c 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.983: [upektc_img] CAPTURE_NUM_STATES entering state 3 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.984: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.984: request completed, len: 0000 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.984: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.985: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.985: 18th byte is 13 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.985: [upektc_img] CAPTURE_NUM_STATES entering state 3 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.986: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.986: request completed, len: 0000 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.986: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.987: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.987: 18th byte is 00 150s (process:3014): libfprint-device-DEBUG: 05:37:54.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.987: [upektc_img] CAPTURE_NUM_STATES entering state 3 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.987: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.988: request completed, len: 0000 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.988: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.989: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.989: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.989: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.989: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.989: request completed, len: 07c4 150s (process:3014): libfprint-image_device-DEBUG: 05:37:54.989: Image device reported finger status: on 150s (process:3014): libfprint-image_device-DEBUG: 05:37:54.989: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.989: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.990: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.991: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.991: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.991: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.991: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.991: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.991: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.992: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.992: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.992: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.992: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.992: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.993: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.993: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.994: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.994: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.994: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.994: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.994: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.995: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.995: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.996: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.996: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.996: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.996: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.996: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.997: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.997: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.998: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.998: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.998: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.998: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.998: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:54.999: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:54.999: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.000: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.001: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.001: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.001: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.001: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.001: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.001: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.002: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.003: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.003: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.003: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.003: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.003: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.003: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.004: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.005: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.005: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.005: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.005: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.005: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.005: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.006: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.006: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.006: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.006: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.006: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.007: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.007: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.008: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.008: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.008: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.008: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.008: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.009: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.009: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.010: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.010: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.010: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.010: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.010: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.011: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.011: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.012: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.014: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.014: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.014: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.014: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.016: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.016: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.016: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.017: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.017: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.017: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.017: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.018: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.018: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.019: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.020: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.020: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.020: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.020: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.021: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.021: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.021: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.022: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.022: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.022: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.022: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.023: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.023: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.024: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.025: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.025: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.025: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.025: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.026: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.026: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.026: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.027: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.027: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.027: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.027: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.028: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.028: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.029: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.030: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.030: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.030: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.030: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.030: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.030: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.031: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.032: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.032: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.032: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.032: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.033: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.033: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.034: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.035: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.035: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.035: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.035: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.035: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.035: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.036: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.037: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.037: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.037: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.037: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.038: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.038: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.039: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.040: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.040: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.040: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.040: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.040: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.041: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.041: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.042: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.042: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.042: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.042: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.043: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.043: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.044: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.045: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.045: response_size is 2052, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.045: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.045: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.045: request completed, len: 07c4 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.045: [upektc_img] CAPTURE_NUM_STATES entering state 5 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.046: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.051: request completed, len: 0040 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.051: response_size is 814, actual_length is 64 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.051: Waiting for rest of transfer 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.051: [upektc_img] CAPTURE_NUM_STATES entering state 1 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.052: request completed, len: 02ee 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.052: Image size is 51840 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.052: Image device captured an image 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.052: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 150s (process:3014): libfprint-device-DEBUG: 05:37:55.056: Device reported finger status change: FP_FINGER_STATUS_PRESENT 150s (process:3014): libfprint-device-DEBUG: 05:37:55.056: Device reported finger status change: FP_FINGER_STATUS_NONE 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.056: Image device reported finger status: off 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.056: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.056: Deactivating image device 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.056: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.056: [upektc_img] CAPTURE_NUM_STATES completed successfully 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.056: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.059: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 150s (process:3014): libfprint-SSM-DEBUG: 05:37:55.060: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 150s (process:3014): libfprint-upektc_img-DEBUG: 05:37:55.060: Deactivate completed 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.060: Image device deactivation completed 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.060: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 150s (process:3014): libfprint-device-DEBUG: 05:37:55.069: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 150s (process:3014): libfprint-image-DEBUG: 05:37:55.080: Minutiae scan completed in 0.027488 secs 150s (process:3014): libfprint-device-DEBUG: 05:37:55.080: Device reported capture completion 150s (process:3014): libfprint-device-DEBUG: 05:37:55.080: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 150s (process:3014): libfprint-device-DEBUG: 05:37:55.080: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s (process:3014): libfprint-image_device-DEBUG: 05:37:55.081: Image device close completed 150s (process:3014): libfprint-device-DEBUG: 05:37:55.081: Device reported close completion 150s (process:3014): libfprint-device-DEBUG: 05:37:55.081: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 150s (process:3014): libfprint-device-DEBUG: 05:37:55.081: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s ** (umockdev-run:3010): DEBUG: 05:37:55.197: umockdev.vala:154: Removing test bed /tmp/umockdev.8JU512 150s (umockdev-run:3010): GLib-DEBUG: 05:37:55.206: unsetenv() is not thread-safe and should not be used after threads are created 150s Comparing PNGs /tmp/libfprint-umockdev-test-2hvvpzfi/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 150s PASS: libfprint-2/driver-upektc_img-tcs1s.test 150s Running test: libfprint-2/driver-vfs5011.test 150s ** (umockdev-run:3023): DEBUG: 05:37:55.302: umockdev.vala:127: Created udev test bed /tmp/umockdev.H2AJ22 150s ** (umockdev-run:3023): DEBUG: 05:37:55.302: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 150s ** (umockdev-run:3023): DEBUG: 05:37:55.303: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 150s ** (umockdev-run:3023): DEBUG: 05:37:55.307: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.H2AJ22/dev/bus/usb/002/017 150s ** (umockdev-run:3023): DEBUG: 05:37:55.307: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 150s ** (umockdev-run:3023): DEBUG: 05:37:55.308: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 150s ** (umockdev-run:3023): DEBUG: 05:37:55.311: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.H2AJ22/dev/bus/usb/002/001 150s ** (umockdev-run:3023): DEBUG: 05:37:55.311: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 150s ** (umockdev-run:3023): DEBUG: 05:37:55.311: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 150s (umockdev-run:3023): GLib-GIO-DEBUG: 05:37:55.314: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 150s (process:3027): libfprint-context-DEBUG: 05:37:55.425: Initializing FpContext (libfprint version 1.94.9+tod1) 150s (process:3027): libfprint-tod-DEBUG: 05:37:55.425: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 150s (process:3027): libfprint-context-DEBUG: 05:37:55.427: No driver found for USB device 1D6B:0002 150s (process:3027): libfprint-device-DEBUG: 05:37:55.428: Device reported probe completion 150s (process:3027): libfprint-device-DEBUG: 05:37:55.428: Completing action FPI_DEVICE_ACTION_PROBE in idle! 150s (process:3027): libfprint-device-DEBUG: 05:37:55.428: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.432: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.432: [vfs5011] DEVICE OPEN entering state 0 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.432: Sending vfs5011_cmd_01 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.432: [vfs5011] DEVICE OPEN entering state 1 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.432: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.433: Got 38 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.433: [vfs5011] DEVICE OPEN entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.433: Sending vfs5011_cmd_19 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.434: [vfs5011] DEVICE OPEN entering state 3 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.434: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.434: Got 64 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.434: [vfs5011] DEVICE OPEN entering state 4 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.434: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.435: Got 4 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.435: [vfs5011] DEVICE OPEN entering state 5 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.435: Sending vfs5011_init_00 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.435: [vfs5011] DEVICE OPEN entering state 6 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.436: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.436: Got 6 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.436: [vfs5011] DEVICE OPEN entering state 7 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.436: Sending vfs5011_init_01 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.437: [vfs5011] DEVICE OPEN entering state 8 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.437: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.438: Got 7 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.438: [vfs5011] DEVICE OPEN entering state 9 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.438: Sending vfs5011_init_02 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.438: [vfs5011] DEVICE OPEN entering state 10 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.438: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.439: [vfs5011] DEVICE OPEN entering state 11 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.439: Sending vfs5011_cmd_01 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.439: [vfs5011] DEVICE OPEN entering state 12 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.439: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.440: Got 38 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.440: [vfs5011] DEVICE OPEN entering state 13 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.440: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.440: [vfs5011] DEVICE OPEN entering state 14 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.440: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.441: [vfs5011] DEVICE OPEN entering state 15 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.441: Sending vfs5011_init_03 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.442: [vfs5011] DEVICE OPEN entering state 16 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.442: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.442: [vfs5011] DEVICE OPEN entering state 17 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.442: Sending vfs5011_init_04 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.443: [vfs5011] DEVICE OPEN entering state 18 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.443: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.444: [vfs5011] DEVICE OPEN entering state 19 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.444: Receiving 256 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.445: Got 256 bytes out of 256 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.445: [vfs5011] DEVICE OPEN entering state 20 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.445: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.446: Got 32 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.446: [vfs5011] DEVICE OPEN entering state 21 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.446: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.447: [vfs5011] DEVICE OPEN entering state 22 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.447: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.447: [vfs5011] DEVICE OPEN entering state 23 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.447: Sending vfs5011_init_05 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.448: [vfs5011] DEVICE OPEN entering state 24 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.448: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.448: [vfs5011] DEVICE OPEN entering state 25 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.448: Sending vfs5011_cmd_01 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.449: [vfs5011] DEVICE OPEN entering state 26 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.449: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.450: Got 38 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.450: [vfs5011] DEVICE OPEN entering state 27 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.450: Sending vfs5011_init_06 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.450: [vfs5011] DEVICE OPEN entering state 28 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.450: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.451: [vfs5011] DEVICE OPEN entering state 29 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.451: Receiving 17216 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.452: Got 17216 bytes out of 17216 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.452: [vfs5011] DEVICE OPEN entering state 30 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.452: Receiving 32 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.452: Got 32 bytes out of 32 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.452: [vfs5011] DEVICE OPEN entering state 31 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.452: Sending vfs5011_init_07 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.453: [vfs5011] DEVICE OPEN entering state 32 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.453: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.453: [vfs5011] DEVICE OPEN entering state 33 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.453: Receiving 45056 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.454: Got 45056 bytes out of 45056 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.454: [vfs5011] DEVICE OPEN entering state 34 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.454: Sending vfs5011_init_08 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.455: [vfs5011] DEVICE OPEN entering state 35 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.455: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.455: [vfs5011] DEVICE OPEN entering state 36 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.455: Receiving 16896 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.457: Got 16896 bytes out of 16896 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.457: [vfs5011] DEVICE OPEN entering state 37 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.457: Sending vfs5011_init_09 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.457: [vfs5011] DEVICE OPEN entering state 38 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.457: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.458: [vfs5011] DEVICE OPEN entering state 39 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.458: Receiving 4928 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.459: Got 4928 bytes out of 4928 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.459: [vfs5011] DEVICE OPEN entering state 40 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.459: Sending vfs5011_init_10 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.460: [vfs5011] DEVICE OPEN entering state 41 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.460: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.461: [vfs5011] DEVICE OPEN entering state 42 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.461: Receiving 5632 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.462: Got 5632 bytes out of 5632 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.462: [vfs5011] DEVICE OPEN entering state 43 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.462: Sending vfs5011_init_11 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.463: [vfs5011] DEVICE OPEN entering state 44 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.463: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.464: [vfs5011] DEVICE OPEN entering state 45 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.464: Receiving 5632 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.465: Got 5632 bytes out of 5632 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.465: [vfs5011] DEVICE OPEN entering state 46 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.465: Sending vfs5011_init_12 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.466: [vfs5011] DEVICE OPEN entering state 47 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.466: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.467: [vfs5011] DEVICE OPEN entering state 48 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.467: Receiving 3328 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.472: Got 3328 bytes out of 3328 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.472: [vfs5011] DEVICE OPEN entering state 49 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.472: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.473: Got 32 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.473: [vfs5011] DEVICE OPEN entering state 50 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.473: Sending vfs5011_init_13 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.474: [vfs5011] DEVICE OPEN entering state 51 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.474: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.474: [vfs5011] DEVICE OPEN entering state 52 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.474: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.475: [vfs5011] DEVICE OPEN entering state 53 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.475: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.476: [vfs5011] DEVICE OPEN entering state 54 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.476: Sending vfs5011_init_03 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.477: [vfs5011] DEVICE OPEN entering state 55 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.477: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.478: [vfs5011] DEVICE OPEN entering state 56 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.478: Sending vfs5011_init_14 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.479: [vfs5011] DEVICE OPEN entering state 57 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.479: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.480: [vfs5011] DEVICE OPEN entering state 58 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.480: Receiving 4800 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.481: Got 4800 bytes out of 4800 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.481: [vfs5011] DEVICE OPEN entering state 59 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.481: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.482: [vfs5011] DEVICE OPEN entering state 60 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.482: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.483: [vfs5011] DEVICE OPEN entering state 61 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.483: Sending vfs5011_init_02 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.484: [vfs5011] DEVICE OPEN entering state 62 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.484: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.484: [vfs5011] DEVICE OPEN entering state 63 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.484: Sending vfs5011_cmd_27 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.485: [vfs5011] DEVICE OPEN entering state 64 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.485: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.486: Got 22 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.486: [vfs5011] DEVICE OPEN entering state 65 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.486: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.487: [vfs5011] DEVICE OPEN entering state 66 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.487: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.488: [vfs5011] DEVICE OPEN entering state 67 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.488: Sending vfs5011_init_15 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.489: [vfs5011] DEVICE OPEN entering state 68 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.489: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.490: [vfs5011] DEVICE OPEN entering state 69 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.490: Sending vfs5011_init_16 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.491: [vfs5011] DEVICE OPEN entering state 70 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.491: Receiving 2368 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.492: Got 2368 bytes out of 2368 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.492: [vfs5011] DEVICE OPEN entering state 71 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.492: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.493: Got 36 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.493: [vfs5011] DEVICE OPEN entering state 72 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.493: Receiving 4800 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.494: Got 4800 bytes out of 4800 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.494: [vfs5011] DEVICE OPEN entering state 73 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.494: Sending vfs5011_init_17 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.495: [vfs5011] DEVICE OPEN entering state 74 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.495: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.496: [vfs5011] DEVICE OPEN entering state 75 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.496: Sending vfs5011_init_18 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.497: [vfs5011] DEVICE OPEN entering state 76 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.497: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.498: [vfs5011] DEVICE OPEN completed successfully 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.498: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.498: Image device open completed 150s (process:3027): libfprint-device-DEBUG: 05:37:55.498: Device reported open completion 150s (process:3027): libfprint-device-DEBUG: 05:37:55.498: Completing action FPI_DEVICE_ACTION_OPEN in idle! 150s (process:3027): libfprint-device-DEBUG: 05:37:55.498: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 150s (process:3027): libfprint-device-DEBUG: 05:37:55.499: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.499: Activating image device 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.499: device initialized 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.499: creating ssm 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.499: starting ssm 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.499: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.499: main_loop: state 0 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.499: [vfs5011] ACTIVATE REQUEST entering state 0 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.499: Sending vfs5011_cmd_04 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.499: ssm done, getting out 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.500: [vfs5011] ACTIVATE REQUEST entering state 1 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.500: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.501: Got 64 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.501: [vfs5011] ACTIVATE REQUEST entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.501: Receiving 84032 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.502: Got 176 bytes out of 84032 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.502: [vfs5011] ACTIVATE REQUEST entering state 3 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.502: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.504: [vfs5011] ACTIVATE REQUEST entering state 4 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.504: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.504: [vfs5011] ACTIVATE REQUEST entering state 5 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.505: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.505: [vfs5011] ACTIVATE REQUEST entering state 6 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.505: Sending vfs5011_prepare_00 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.506: [vfs5011] ACTIVATE REQUEST entering state 7 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.506: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.507: [vfs5011] ACTIVATE REQUEST entering state 8 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.507: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.508: [vfs5011] ACTIVATE REQUEST entering state 9 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.508: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.509: [vfs5011] ACTIVATE REQUEST entering state 10 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.509: Sending vfs5011_prepare_01 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.510: [vfs5011] ACTIVATE REQUEST entering state 11 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.510: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.511: [vfs5011] ACTIVATE REQUEST entering state 12 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.511: Sending vfs5011_prepare_02 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.512: [vfs5011] ACTIVATE REQUEST entering state 13 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.512: Receiving 2368 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.513: Got 2368 bytes out of 2368 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.513: [vfs5011] ACTIVATE REQUEST entering state 14 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.513: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.514: Got 36 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.514: [vfs5011] ACTIVATE REQUEST entering state 15 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.514: Receiving 4800 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.515: Got 4800 bytes out of 4800 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.515: [vfs5011] ACTIVATE REQUEST entering state 16 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.515: Sending vfs5011_prepare_03 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.516: [vfs5011] ACTIVATE REQUEST entering state 17 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.516: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.517: [vfs5011] ACTIVATE REQUEST entering state 18 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.517: Sending vfs5011_prepare_04 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.518: [vfs5011] ACTIVATE REQUEST entering state 19 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.518: Receiving 2368 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.518: [vfs5011] ACTIVATE REQUEST completed successfully 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.518: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.518: main_loop: state 1 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.518: capture_init 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.519: Image device activation completed 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.519: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.519: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 150s (process:3027): libfprint-device-DEBUG: 05:37:55.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.519: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.519: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.519: capture_chunk_async: capture 256 lines, already have 0 150s (process:3027): libfprint-device-DEBUG: 05:37:55.520: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.520: Image device reported finger status: on 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.520: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.520: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.520: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.520: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.520: capture_chunk_async: capture 256 lines, already have 6 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.521: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.521: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.521: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.521: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.521: capture_chunk_async: capture 256 lines, already have 25 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.522: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.522: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.522: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.522: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.522: capture_chunk_async: capture 256 lines, already have 54 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.523: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.523: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.523: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.523: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.523: capture_chunk_async: capture 256 lines, already have 89 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.524: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.524: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.524: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.524: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.524: capture_chunk_async: capture 256 lines, already have 117 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.525: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.525: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.525: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.525: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.525: capture_chunk_async: capture 256 lines, already have 144 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.526: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.526: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.526: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.526: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.526: capture_chunk_async: capture 256 lines, already have 180 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.527: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.527: process_chunk: got 61440 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.527: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.527: main_loop: state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.527: capture_chunk_async: capture 256 lines, already have 273 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.528: Image device reported finger status: on 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.528: process_chunk: got 61440 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.528: process_chunk: got 50 empty lines, finishing 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.528: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.528: main_loop: state 3 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.529: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.529: main_loop: state 4 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.529: [vfs5011] PREPARE CAPTURE entering state 0 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.529: Sending vfs5011_cmd_04 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.530: [vfs5011] PREPARE CAPTURE entering state 1 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.530: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.530: Got 64 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.531: [vfs5011] PREPARE CAPTURE entering state 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.531: Receiving 84032 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.531: Got 176 bytes out of 84032 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.531: [vfs5011] PREPARE CAPTURE entering state 3 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.531: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.532: [vfs5011] PREPARE CAPTURE entering state 4 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.532: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.533: [vfs5011] PREPARE CAPTURE entering state 5 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.533: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.534: [vfs5011] PREPARE CAPTURE entering state 6 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.534: Sending vfs5011_prepare_00 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.534: [vfs5011] PREPARE CAPTURE entering state 7 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.534: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.535: [vfs5011] PREPARE CAPTURE entering state 8 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.535: Sending vfs5011_cmd_1A 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.536: [vfs5011] PREPARE CAPTURE entering state 9 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.536: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.536: [vfs5011] PREPARE CAPTURE entering state 10 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.536: Sending vfs5011_prepare_01 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.537: [vfs5011] PREPARE CAPTURE entering state 11 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.537: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.538: [vfs5011] PREPARE CAPTURE entering state 12 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.538: Sending vfs5011_prepare_02 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.539: [vfs5011] PREPARE CAPTURE entering state 13 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.539: Receiving 2368 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.539: Got 2368 bytes out of 2368 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.539: [vfs5011] PREPARE CAPTURE entering state 14 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.539: Receiving 64 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.540: Got 36 bytes out of 64 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.540: [vfs5011] PREPARE CAPTURE entering state 15 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.540: Receiving 4800 bytes 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.541: Got 4800 bytes out of 4800 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.541: [vfs5011] PREPARE CAPTURE entering state 16 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.541: Sending vfs5011_prepare_03 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.542: [vfs5011] PREPARE CAPTURE entering state 17 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.542: Receiving 64 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.542: [vfs5011] PREPARE CAPTURE entering state 18 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.542: Sending vfs5011_prepare_04 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.543: [vfs5011] PREPARE CAPTURE entering state 19 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.543: Receiving 2368 bytes 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.544: [vfs5011] PREPARE CAPTURE completed successfully 150s (process:3027): libfprint-SSM-DEBUG: 05:37:55.544: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.544: finishing 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 1740202675544590 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 1 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 4 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 4 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 3 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 3 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 4 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.544: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 4 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 4 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 11 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 30 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 26 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 4 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.545: 2 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: offsets_filtered: 1740202675546175 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 5 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 27 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 29 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 28 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 6 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 9 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 8 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 7 150s (process:3027): libfprint-assembling-DEBUG: 05:37:55.546: 2 150s (process:3027): libfprint-vfs5011-DEBUG: 05:37:55.547: Image captured, committing 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.547: Image device captured an image 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 150s (process:3027): libfprint-device-DEBUG: 05:37:55.552: Device reported finger status change: FP_FINGER_STATUS_PRESENT 150s (process:3027): libfprint-device-DEBUG: 05:37:55.552: Device reported finger status change: FP_FINGER_STATUS_NONE 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.552: Image device reported finger status: off 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.552: Deactivating image device 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.552: Image device deactivation completed 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 150s (process:3027): libfprint-image-DEBUG: 05:37:55.583: Minutiae scan completed in 0.034859 secs 150s (process:3027): libfprint-device-DEBUG: 05:37:55.583: Device reported capture completion 150s (process:3027): libfprint-device-DEBUG: 05:37:55.583: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 150s (process:3027): libfprint-device-DEBUG: 05:37:55.583: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 150s (process:3027): libfprint-image_device-DEBUG: 05:37:55.583: Image device close completed 150s (process:3027): libfprint-device-DEBUG: 05:37:55.583: Device reported close completion 150s (process:3027): libfprint-device-DEBUG: 05:37:55.584: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 150s (process:3027): libfprint-device-DEBUG: 05:37:55.584: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 150s ** (umockdev-run:3023): DEBUG: 05:37:55.737: umockdev.vala:154: Removing test bed /tmp/umockdev.H2AJ22 150s (umockdev-run:3023): GLib-DEBUG: 05:37:55.746: unsetenv() is not thread-safe and should not be used after threads are created 150s Comparing PNGs /tmp/libfprint-umockdev-test-l_nojncv/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 150s PASS: libfprint-2/driver-vfs5011.test 150s Running test: libfprint-2/driver-aes3500.test 150s ** (umockdev-run:3036): DEBUG: 05:37:55.858: umockdev.vala:127: Created udev test bed /tmp/umockdev.NXX512 150s ** (umockdev-run:3036): DEBUG: 05:37:55.858: 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 150s ** (umockdev-run:3036): DEBUG: 05:37:55.863: 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) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.867: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NXX512/dev/bus/usb/003/004 150s ** (umockdev-run:3036): DEBUG: 05:37:55.867: 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 150s ** (umockdev-run:3036): DEBUG: 05:37:55.870: 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) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.873: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NXX512/dev/bus/usb/003/003 150s ** (umockdev-run:3036): DEBUG: 05:37:55.873: 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 150s ** (umockdev-run:3036): DEBUG: 05:37:55.875: 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) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.879: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NXX512/dev/bus/usb/003/002 150s ** (umockdev-run:3036): DEBUG: 05:37:55.879: 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 150s ** (umockdev-run:3036): DEBUG: 05:37:55.882: 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) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.885: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.NXX512/dev/bus/usb/003/001 150s ** (umockdev-run:3036): DEBUG: 05:37:55.885: 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 150s ** (umockdev-run:3036): DEBUG: 05:37:55.886: 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) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.890: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 150s ** (umockdev-run:3036): DEBUG: 05:37:55.891: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.894: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 150s ** (umockdev-run:3036): DEBUG: 05:37:55.895: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 150s ** (umockdev-run:3036): DEBUG: 05:37:55.898: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 150s ** (umockdev-run:3036): DEBUG: 05:37:55.899: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 150s (umockdev-run:3036): GLib-GIO-DEBUG: 05:37:55.902: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 151s (process:3040): libfprint-context-DEBUG: 05:37:56.012: Initializing FpContext (libfprint version 1.94.9+tod1) 151s (process:3040): libfprint-tod-DEBUG: 05:37:56.012: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 151s (process:3040): libfprint-context-DEBUG: 05:37:56.017: No driver found for USB device 2230:0006 151s (process:3040): libfprint-context-DEBUG: 05:37:56.017: No driver found for USB device 2230:0006 151s (process:3040): libfprint-context-DEBUG: 05:37:56.017: No driver found for USB device 1D6B:0002 151s (process:3040): libfprint-device-DEBUG: 05:37:56.017: Device reported probe completion 151s (process:3040): libfprint-device-DEBUG: 05:37:56.017: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s (process:3040): libfprint-device-DEBUG: 05:37:56.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.019: Image device open completed 151s (process:3040): libfprint-device-DEBUG: 05:37:56.019: Device reported open completion 151s (process:3040): libfprint-device-DEBUG: 05:37:56.019: Completing action FPI_DEVICE_ACTION_OPEN in idle! 151s (process:3040): libfprint-device-DEBUG: 05:37:56.019: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (process:3040): libfprint-device-DEBUG: 05:37:56.019: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.019: Activating image device 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.019: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 151s (process:3040): libfprint-aeslib-DEBUG: 05:37:56.019: write 50 regs 151s (process:3040): libfprint-aeslib-DEBUG: 05:37:56.025: all registers written 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.025: Image device activation completed 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.025: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.025: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:3040): libfprint-aeslib-DEBUG: 05:37:56.025: write 6 regs 151s (process:3040): libfprint-device-DEBUG: 05:37:56.025: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:3040): libfprint-aeslib-DEBUG: 05:37:56.027: all registers written 151s (process:3040): libfprint-device-DEBUG: 05:37:56.028: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.028: Image device reported finger status: on 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e0 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e1 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e2 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e3 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e4 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e5 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e6 151s (process:3040): libfprint-aes3k-DEBUG: 05:37:56.028: frame header byte e7 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.028: Image device captured an image 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:3040): libfprint-device-DEBUG: 05:37:56.029: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:3040): libfprint-device-DEBUG: 05:37:56.029: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Image device reported finger status: off 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Deactivating image device 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Image device deactivation completed 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.029: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 151s (process:3040): libfprint-image-DEBUG: 05:37:56.051: Minutiae scan completed in 0.022217 secs 151s (process:3040): libfprint-device-DEBUG: 05:37:56.051: Device reported capture completion 151s (process:3040): libfprint-device-DEBUG: 05:37:56.051: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 151s (process:3040): libfprint-device-DEBUG: 05:37:56.051: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 151s (process:3040): libfprint-image_device-DEBUG: 05:37:56.052: Image device close completed 151s (process:3040): libfprint-device-DEBUG: 05:37:56.052: Device reported close completion 151s (process:3040): libfprint-device-DEBUG: 05:37:56.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 151s (process:3040): libfprint-device-DEBUG: 05:37:56.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s ** (umockdev-run:3036): DEBUG: 05:37:56.211: umockdev.vala:154: Removing test bed /tmp/umockdev.NXX512 151s (umockdev-run:3036): GLib-DEBUG: 05:37:56.229: unsetenv() is not thread-safe and should not be used after threads are created 151s Comparing PNGs /tmp/libfprint-umockdev-test-jg4ol462/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 151s PASS: libfprint-2/driver-aes3500.test 151s Running test: libfprint-2/driver-uru4000-4500.test 151s ** (umockdev-run:3049): DEBUG: 05:37:56.324: umockdev.vala:127: Created udev test bed /tmp/umockdev.C1PI22 151s ** (umockdev-run:3049): DEBUG: 05:37:56.324: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 151s ** (umockdev-run:3049): DEBUG: 05:37:56.326: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 151s ** (umockdev-run:3049): DEBUG: 05:37:56.328: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.C1PI22/dev/bus/usb/001/050 151s ** (umockdev-run:3049): DEBUG: 05:37:56.329: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 151s ** (umockdev-run:3049): DEBUG: 05:37:56.331: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 151s ** (umockdev-run:3049): DEBUG: 05:37:56.335: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.C1PI22/dev/bus/usb/001/001 151s ** (umockdev-run:3049): DEBUG: 05:37:56.335: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 151s ** (umockdev-run:3049): DEBUG: 05:37:56.335: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 151s (process:3053): libfprint-context-DEBUG: 05:37:56.436: Initializing FpContext (libfprint version 1.94.9+tod1) 151s (process:3053): libfprint-tod-DEBUG: 05:37:56.437: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 151s (process:3053): libfprint-context-DEBUG: 05:37:56.440: No driver found for USB device 1D6B:0002 151s (process:3053): libfprint-device-DEBUG: 05:37:56.441: Device reported probe completion 151s (process:3053): libfprint-device-DEBUG: 05:37:56.441: Completing action FPI_DEVICE_ACTION_PROBE in idle! 151s (process:3053): libfprint-device-DEBUG: 05:37:56.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.445: Image device open completed 151s (process:3053): libfprint-device-DEBUG: 05:37:56.445: Device reported open completion 151s (process:3053): libfprint-device-DEBUG: 05:37:56.445: Completing action FPI_DEVICE_ACTION_OPEN in idle! 151s (process:3053): libfprint-device-DEBUG: 05:37:56.445: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (process:3053): libfprint-device-DEBUG: 05:37:56.445: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.445: Activating image device 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.445: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.446: [uru4000] INIT_NUM_STATES entering state 0 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.446: read 1 regs at 7 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.447: reg value 1 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.447: [uru4000] INIT_NUM_STATES entering state 1 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.447: [uru4000] INIT_NUM_STATES entering state 3 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.447: set 81 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.447: [uru4000] INIT_NUM_STATES entering state 4 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.447: [uru4000] POWERUP_NUM_STATES entering state 0 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.447: [uru4000] POWERUP_NUM_STATES entering state 1 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.447: set 01 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.448: recv irq type 56aa 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.448: early scanpwr interrupt 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.449: [uru4000] POWERUP_NUM_STATES entering state 2 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.449: read 1 regs at 7 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.449: reg value 1 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.449: [uru4000] POWERUP_NUM_STATES entering state 3 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.449: [uru4000] POWERUP_NUM_STATES completed successfully 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.449: [uru4000] INIT_NUM_STATES entering state 5 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.449: [uru4000] INIT_NUM_STATES entering state 6 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.449: [uru4000] INIT_NUM_STATES entering state 7 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.449: read 16 regs at f0 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.450: reg value 1a 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.450: [uru4000] INIT_NUM_STATES entering state 8 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.450: Versions 0010 and 0115 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.450: [uru4000] INIT_NUM_STATES completed successfully 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.450: Image device activation completed 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.450: wait finger on 151s (process:3053): libfprint-device-DEBUG: 05:37:56.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.451: recv irq type 56aa 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.452: recv irq type 56aa 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.453: recv irq type 0101 151s (process:3053): libfprint-device-DEBUG: 05:37:56.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.453: Image device reported finger status: on 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.453: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.453: starting capture 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.453: Image encryption seed: 1374298404 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.453: [uru4000] IMAGING_NUM_STATES entering state 0 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.454: [uru4000] IMAGING_NUM_STATES entering state 1 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.454: hw header lines 289 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.454: dev2: 11240 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.454: image seems to be encrypted 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.455: [uru4000] IMAGING_NUM_STATES entering state 2 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.455: read 4 regs at 34 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.455: reg value f2 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.455: [uru4000] IMAGING_NUM_STATES entering state 3 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.455: encryption id 00 -> key 544409d6 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.455: 0 02 72 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.455: decoding 72 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 1 00 1 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: skipping 1 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 2 02 49 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: decoding 49 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 3 01 1 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: skipping 1 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 4 00 1 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: skipping 1 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 5 02 49 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: decoding 49 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 6 00 1 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: skipping 1 lines 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: 7 02 116 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.456: decoding 116 lines 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.456: [uru4000] IMAGING_NUM_STATES entering state 4 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.456: Image device captured an image 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.456: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 151s (process:3053): libfprint-device-DEBUG: 05:37:56.457: Device reported finger status change: FP_FINGER_STATUS_PRESENT 151s (process:3053): libfprint-SSM-DEBUG: 05:37:56.460: [uru4000] IMAGING_NUM_STATES completed successfully 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.460: await finger off 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.461: recv irq type 0200 151s (process:3053): libfprint-device-DEBUG: 05:37:56.461: Device reported finger status change: FP_FINGER_STATUS_NONE 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.461: Image device reported finger status: off 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.461: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.461: Deactivating image device 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.461: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.461: deactivating 151s (process:3053): libfprint-uru4000-DEBUG: 05:37:56.462: cancelled 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.462: Image device deactivation completed 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.462: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 151s (process:3053): libfprint-image-DEBUG: 05:37:56.481: Minutiae scan completed in 0.024189 secs 151s (process:3053): libfprint-device-DEBUG: 05:37:56.481: Device reported capture completion 151s (process:3053): libfprint-device-DEBUG: 05:37:56.481: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 151s (process:3053): libfprint-device-DEBUG: 05:37:56.481: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 151s (process:3053): libfprint-image_device-DEBUG: 05:37:56.482: Image device close completed 151s (process:3053): libfprint-device-DEBUG: 05:37:56.482: Device reported close completion 151s (process:3053): libfprint-device-DEBUG: 05:37:56.482: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 151s (process:3053): libfprint-device-DEBUG: 05:37:56.482: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 151s ** (umockdev-run:3049): DEBUG: 05:37:56.716: umockdev.vala:154: Removing test bed /tmp/umockdev.C1PI22 151s (umockdev-run:3049): GLib-DEBUG: 05:37:56.726: unsetenv() is not thread-safe and should not be used after threads are created 151s Comparing PNGs /tmp/libfprint-umockdev-test-9qg99y_n/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 151s PASS: libfprint-2/driver-uru4000-4500.test 151s Running test: libfprint-2/driver-egismoc-0587.test 151s ** (umockdev-run:3062): DEBUG: 05:37:56.842: umockdev.vala:127: Created udev test bed /tmp/umockdev.FFQ712 151s ** (umockdev-run:3062): DEBUG: 05:37:56.842: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 151s ** (umockdev-run:3062): DEBUG: 05:37:56.845: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 151s ** (umockdev-run:3062): DEBUG: 05:37:56.851: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FFQ712/dev/bus/usb/003/009 151s ** (umockdev-run:3062): DEBUG: 05:37:56.851: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 151s ** (umockdev-run:3062): DEBUG: 05:37:56.854: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 151s ** (umockdev-run:3062): DEBUG: 05:37:56.860: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FFQ712/dev/bus/usb/003/001 151s ** (umockdev-run:3062): DEBUG: 05:37:56.861: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 151s ** (umockdev-run:3062): DEBUG: 05:37:56.862: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 152s (process:3066): libfprint-context-DEBUG: 05:37:57.022: Initializing FpContext (libfprint version 1.94.9+tod1) 152s (process:3066): libfprint-tod-DEBUG: 05:37:57.022: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.026: 97865997: ../libfprint/drivers/egismoc/egismoc.c:1597 152s (process:3066): libfprint-context-DEBUG: 05:37:57.026: No driver found for USB device 1D6B:0002 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.027: egismoc_probe enter --> 152s (process:3066): libfprint-device-DEBUG: 05:37:57.028: Device reported probe completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.029: Completing action FPI_DEVICE_ACTION_PROBE in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.030: Opening device 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.030: [egismoc] DEV_INIT_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.031: [egismoc] DEV_INIT_STATES entering state 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.032: [egismoc] DEV_INIT_STATES entering state 2 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.032: [egismoc] DEV_INIT_STATES entering state 3 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.033: [egismoc] DEV_INIT_STATES entering state 4 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.034: [egismoc] DEV_INIT_STATES entering state 5 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.034: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.034: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.034: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.035: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.036: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.036: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.036: Firmware version callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.036: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.036: Device firmware version is 9050.6.4.67 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.036: [egismoc] DEV_INIT_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.036: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.036: Device reported open completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.036: Completing action FPI_DEVICE_ACTION_OPEN in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.036: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.036: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.037: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.037: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.037: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.037: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.037: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.038: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.038: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.038: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.038: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.038: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.038: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: Clear storage 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.038: [egismoc] DELETE_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.038: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.039: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.039: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.039: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.040: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.040: [egismoc] DELETE_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: Get delete command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.040: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.040: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.041: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.042: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: Delete callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: Response prefix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.042: Device reported deletion completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.042: [egismoc] DELETE_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.042: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.042: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.042: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.042: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.042: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.042: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.043: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.043: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.043: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.043: Number of currently enrolled fingerprints on the device is 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.043: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.043: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.043: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.043: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.043: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.043: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3066): libfprint-device-DEBUG: 05:37:57.044: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.044: Enroll 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.044: [egismoc] ENROLL_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.044: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.044: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.044: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.045: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.045: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.045: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.045: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.045: Number of currently enrolled fingerprints on the device is 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.045: [egismoc] ENROLL_STATES entering state 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.045: [egismoc] ENROLL_STATES entering state 2 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.045: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.046: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.046: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.046: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.047: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.047: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.047: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.047: [egismoc] ENROLL_STATES entering state 3 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.047: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.047: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.047: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.048: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.048: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.048: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.048: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.048: [egismoc] ENROLL_STATES entering state 4 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.048: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.048: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.049: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.049: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.049: [egismoc] ENROLL_STATES entering state 5 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.049: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.049: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.049: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.050: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.051: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.051: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.051: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.051: [egismoc] ENROLL_STATES entering state 6 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.051: Get check command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.051: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.051: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.051: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.051: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.055: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.055: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.055: Enroll check callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.055: Response suffix valid: yes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.055: [egismoc] ENROLL_STATES entering state 7 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.055: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.055: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.055: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.056: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.057: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.057: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.057: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.057: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.057: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.057: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.057: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.057: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.058: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.058: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.058: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.058: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.058: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.058: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.058: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.059: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.060: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.060: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.060: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.060: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.060: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.061: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.061: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.061: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.061: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.061: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.061: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.062: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.063: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Partial capture successful. Please touch the sensor again (1/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.063: Device reported enroll progress, reported 1 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.063: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.063: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.063: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.063: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.064: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.064: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.064: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.064: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.064: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.064: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.064: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.065: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.066: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.066: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.066: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.066: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.066: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.066: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.066: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.066: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.066: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.066: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.066: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.067: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.068: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Partial capture successful. Please touch the sensor again (2/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.068: Device reported enroll progress, reported 2 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.068: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.068: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.068: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.069: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.069: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.069: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.069: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.069: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.069: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.069: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.069: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.070: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.072: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.072: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.072: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.072: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.072: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.072: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.072: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.072: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.072: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.073: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.073: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.073: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.073: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.074: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Partial capture successful. Please touch the sensor again (3/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.074: Device reported enroll progress, reported 3 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.074: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.074: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.074: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.075: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.076: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.076: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.076: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.076: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.076: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.076: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.076: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.076: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.077: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.077: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.077: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.077: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.077: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.078: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.078: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.078: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.078: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.078: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.078: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.079: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.080: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Partial capture successful. Please touch the sensor again (4/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.080: Device reported enroll progress, reported 4 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.080: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.080: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.080: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.080: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.081: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.081: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.081: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.081: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.081: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.081: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.081: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.082: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.082: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.082: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.082: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.082: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.082: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.083: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.083: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.083: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.083: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.083: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.083: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.084: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.084: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.084: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.084: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.084: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.084: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.084: Partial capture successful. Please touch the sensor again (5/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.084: Device reported enroll progress, reported 5 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.085: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.085: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.085: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.085: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.085: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.086: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.086: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.086: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.086: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.086: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.086: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.086: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.087: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.087: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.087: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.087: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.087: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.087: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.087: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.088: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.088: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.088: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.088: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.088: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.088: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.089: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.090: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Partial capture successful. Please touch the sensor again (6/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.090: Device reported enroll progress, reported 6 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.090: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.090: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.090: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.090: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.091: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.091: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.091: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.091: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.091: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.091: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.091: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.092: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.093: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.093: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.093: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.093: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.093: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.094: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.094: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.094: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.094: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.094: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.094: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.095: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.096: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Partial capture successful. Please touch the sensor again (7/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.096: Device reported enroll progress, reported 7 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.096: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.096: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.096: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.097: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.098: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.098: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.098: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.098: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.098: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.098: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.098: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.098: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.099: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.099: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.099: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.099: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.099: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.100: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.100: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.100: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.100: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.100: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.100: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.101: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.101: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.101: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.101: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.101: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.101: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.101: Partial capture successful. Please touch the sensor again (8/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.101: Device reported enroll progress, reported 8 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.102: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.102: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.102: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.102: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.102: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.103: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.103: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.103: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.103: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.103: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.103: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.103: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.104: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.104: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.104: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.104: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.104: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.104: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.105: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.105: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.105: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.105: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.105: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.105: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.106: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.107: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Partial capture successful. Please touch the sensor again (9/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.107: Device reported enroll progress, reported 9 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.107: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.107: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.107: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.108: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.108: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.108: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.108: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.108: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.108: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.108: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.108: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.109: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.110: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.110: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.110: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.110: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.110: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.110: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.110: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.110: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.110: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.110: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.110: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.111: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.112: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Response suffix valid: NO 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Response suffix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.112: Device reported enroll progress, reported 9 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.112: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.112: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.112: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.113: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.114: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.114: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.114: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.114: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.114: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.114: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.114: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.114: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.115: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.115: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.115: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.115: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.115: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.116: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.116: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.116: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.116: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.116: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.117: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.118: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Partial capture successful. Please touch the sensor again (10/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.118: Device reported enroll progress, reported 10 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.118: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.118: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.118: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.119: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.120: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.120: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.120: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.120: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.120: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.120: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.120: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.120: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.121: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.121: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.121: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.121: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.121: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.122: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.122: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.122: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.122: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.122: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.122: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.123: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.123: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Response suffix valid: NO 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Response suffix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.123: Device reported enroll progress, reported 10 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.123: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.123: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.123: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.124: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.125: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.125: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.125: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.125: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.125: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.125: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.125: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.125: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.126: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.126: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.126: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.126: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.126: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.126: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.127: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.127: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.127: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.127: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.127: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.127: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.127: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.128: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Partial capture successful. Please touch the sensor again (11/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.128: Device reported enroll progress, reported 11 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.128: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.128: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.128: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.129: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.130: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.130: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.130: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.130: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.130: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.130: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.130: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.130: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.131: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.131: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.131: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.131: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.131: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.132: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.132: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.132: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.132: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.132: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.132: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.133: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.133: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Partial capture successful. Please touch the sensor again (12/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.133: Device reported enroll progress, reported 12 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.133: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.133: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.133: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.134: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.135: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.135: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.135: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.135: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.135: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.135: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.135: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.135: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.136: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.136: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.136: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.136: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.136: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.137: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.137: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.137: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.137: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.137: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.137: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.137: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.138: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Partial capture successful. Please touch the sensor again (13/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.138: Device reported enroll progress, reported 13 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.138: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.138: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.138: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.139: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.140: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.140: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.140: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.140: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.140: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.140: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.140: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.140: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.141: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.141: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.141: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.141: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.141: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.142: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.142: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.142: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.142: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.142: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.142: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.142: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.143: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Partial capture successful. Please touch the sensor again (14/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.143: Device reported enroll progress, reported 14 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.143: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.143: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.143: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.144: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.145: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.145: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.145: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.145: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.145: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.145: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.145: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-device-DEBUG: 05:37:57.145: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.145: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.146: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.146: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.146: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.146: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.146: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.147: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.147: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.147: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.147: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.147: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.147: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.148: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.148: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Partial capture successful. Please touch the sensor again (15/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.148: Device reported enroll progress, reported 15 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.148: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.148: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.148: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.149: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.150: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.150: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.150: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.150: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.150: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.150: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.150: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.150: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.151: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.151: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.151: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.151: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.151: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.152: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.152: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.152: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.152: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.152: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.152: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.153: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.153: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Partial capture successful. Please touch the sensor again (16/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.153: Device reported enroll progress, reported 16 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.153: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.153: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.153: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.154: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.155: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.155: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.155: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.155: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.155: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.155: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.155: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.156: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.157: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.157: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.157: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.157: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.157: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.157: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.157: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.157: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.157: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.157: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.157: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.158: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.159: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Partial capture successful. Please touch the sensor again (17/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.159: Device reported enroll progress, reported 17 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.159: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.159: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.159: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.160: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.160: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.160: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.160: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.160: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.160: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.160: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.160: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.161: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.162: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.162: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.162: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.162: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.162: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.162: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.162: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.162: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.162: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.162: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.162: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.162: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.163: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.164: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Partial capture successful. Please touch the sensor again (18/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.164: Device reported enroll progress, reported 18 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.164: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.164: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.164: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.165: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.165: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.165: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.165: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.165: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.165: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.165: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.165: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.166: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.167: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.167: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.167: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.167: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.167: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.168: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.168: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.168: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.168: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.168: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.168: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.168: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.169: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Partial capture successful. Please touch the sensor again (19/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.169: Device reported enroll progress, reported 19 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.169: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.169: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.169: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.170: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.170: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.170: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.170: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.170: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.170: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.170: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.170: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.171: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.172: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.173: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.173: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.173: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.173: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.173: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.174: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.174: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.174: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.174: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.174: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.174: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.174: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.175: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.175: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.175: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.175: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.176: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.176: Partial capture successful. Please touch the sensor again (20/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.176: Device reported enroll progress, reported 20 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.176: [egismoc] ENROLL_STATES entering state 12 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.176: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.176: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.176: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.176: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.177: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.177: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.177: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.177: [egismoc] ENROLL_STATES entering state 13 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.177: New fingerprint ID: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.177: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.177: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.177: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.178: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.179: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.179: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.179: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.179: [egismoc] ENROLL_STATES entering state 14 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.179: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.179: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.179: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.179: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.180: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.180: [egismoc] ENROLL_STATES entering state 15 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: Enrollment was successful! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.180: Device reported enroll completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.180: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:3066): libfprint-device-DEBUG: 05:37:57.180: Print for finger FP_FINGER_LEFT_INDEX enrolled 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.180: [egismoc] ENROLL_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.180: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.180: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.180: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.180: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.180: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.181: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.182: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.182: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.182: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.182: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.182: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-device-DEBUG: 05:37:57.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Identify or Verify 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.182: [egismoc] IDENTIFY_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.182: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.182: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.183: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.188: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.188: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.188: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.188: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.188: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.188: [egismoc] IDENTIFY_STATES entering state 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.188: [egismoc] IDENTIFY_STATES entering state 2 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.188: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.188: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.188: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.188: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.189: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.189: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.189: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.189: [egismoc] IDENTIFY_STATES entering state 3 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.189: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.189: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.189: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.190: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.191: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.191: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.191: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.191: [egismoc] IDENTIFY_STATES entering state 4 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.191: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.191: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.192: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.192: [egismoc] IDENTIFY_STATES entering state 5 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.192: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.192: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.192: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.192: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.193: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.193: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.193: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.193: [egismoc] IDENTIFY_STATES entering state 6 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.193: Get check command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.193: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.193: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.193: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.194: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.194: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.194: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.194: Identify check callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.194: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.195: Identify successful for: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.195: Verifying against: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-device-DEBUG: 05:37:57.195: Device reported verify result 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.195: [egismoc] IDENTIFY_STATES entering state 7 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.195: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.195: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.195: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.196: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.196: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.196: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.196: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.196: [egismoc] IDENTIFY_STATES entering state 8 152s (process:3066): libfprint-device-DEBUG: 05:37:57.196: Device reported verify completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.196: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.196: [egismoc] IDENTIFY_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.196: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.196: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.196: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-device-DEBUG: 05:37:57.197: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.197: Identify or Verify 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.197: [egismoc] IDENTIFY_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.197: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.197: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.197: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.198: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.199: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.199: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.199: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.199: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.199: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.199: [egismoc] IDENTIFY_STATES entering state 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.199: [egismoc] IDENTIFY_STATES entering state 2 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.199: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.199: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.199: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.199: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.200: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.200: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.200: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.200: [egismoc] IDENTIFY_STATES entering state 3 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.200: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.200: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.200: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.201: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.201: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.201: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.201: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.201: [egismoc] IDENTIFY_STATES entering state 4 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.201: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.201: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.202: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.202: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.202: [egismoc] IDENTIFY_STATES entering state 5 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.202: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.202: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.202: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.203: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.204: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.204: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.204: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.204: [egismoc] IDENTIFY_STATES entering state 6 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.204: Get check command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.204: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.204: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.204: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.205: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.206: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.206: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.206: Identify check callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.206: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.206: Identify successful for: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-device-DEBUG: 05:37:57.206: Device reported identify result 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.206: [egismoc] IDENTIFY_STATES entering state 7 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.206: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.206: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.206: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.207: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.207: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.207: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.207: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.207: [egismoc] IDENTIFY_STATES entering state 8 152s (process:3066): libfprint-device-DEBUG: 05:37:57.207: Device reported identify completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.207: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.207: [egismoc] IDENTIFY_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.207: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.208: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.208: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-device-DEBUG: 05:37:57.208: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.208: Enroll 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.208: [egismoc] ENROLL_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.208: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.208: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.208: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.209: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.210: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.210: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.210: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.210: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.210: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.210: [egismoc] ENROLL_STATES entering state 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.210: [egismoc] ENROLL_STATES entering state 2 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.210: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.210: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.210: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.210: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.211: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.211: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.211: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.211: [egismoc] ENROLL_STATES entering state 3 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.211: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.211: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.211: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.212: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.213: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.213: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.213: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.213: [egismoc] ENROLL_STATES entering state 4 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.213: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.213: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.213: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.213: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.213: [egismoc] ENROLL_STATES entering state 5 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.213: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.213: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.213: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.214: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.215: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.215: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.215: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.215: [egismoc] ENROLL_STATES entering state 6 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.215: Get check command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.215: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.215: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.215: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.215: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.216: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.216: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.216: Enroll check callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.216: Response suffix valid: NO 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.216: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.216: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.216: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.216: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 152s (process:3066): libfprint-device-DEBUG: 05:37:57.216: Device reported enroll completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.216: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:3066): libfprint-device-DEBUG: 05:37:57.216: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.216: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.217: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.217: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.217: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.217: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.217: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.218: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.218: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.218: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.218: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.218: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.218: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.218: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.218: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.218: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.218: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.218: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.218: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-device-DEBUG: 05:37:57.219: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.219: Enroll 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.219: [egismoc] ENROLL_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.219: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.219: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.219: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.219: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.220: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.220: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.220: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.220: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.220: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.220: [egismoc] ENROLL_STATES entering state 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.220: [egismoc] ENROLL_STATES entering state 2 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.220: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.220: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.220: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.221: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.222: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.222: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.222: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.222: [egismoc] ENROLL_STATES entering state 3 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.222: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.222: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.222: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.223: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.224: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.224: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.224: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.224: [egismoc] ENROLL_STATES entering state 4 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.224: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.224: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.224: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.224: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.224: [egismoc] ENROLL_STATES entering state 5 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.224: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.224: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.224: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.225: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.226: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.226: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.226: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.226: [egismoc] ENROLL_STATES entering state 6 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.226: Get check command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.226: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.226: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.226: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.227: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.227: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.227: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.227: Enroll check callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.227: Response suffix valid: yes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.227: [egismoc] ENROLL_STATES entering state 7 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.227: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.227: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.227: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.228: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.229: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.229: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.229: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.229: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.229: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.229: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.229: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.230: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.230: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.230: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.231: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.231: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.231: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.231: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.231: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.231: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.232: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.232: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.232: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.232: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.232: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.233: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.233: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.233: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.233: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.233: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.233: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.234: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.234: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Partial capture successful. Please touch the sensor again (1/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.234: Device reported enroll progress, reported 1 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.234: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.234: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.234: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.235: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.236: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.236: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.236: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.236: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.236: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.236: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.236: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.237: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.238: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.238: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.238: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.238: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.238: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.238: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.238: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.238: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.238: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.238: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.238: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.239: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.241: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Partial capture successful. Please touch the sensor again (2/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.241: Device reported enroll progress, reported 2 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.241: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.241: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.241: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.242: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.243: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.243: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.243: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.243: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.243: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.243: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.243: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.244: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.244: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.244: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.244: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.244: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.244: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.244: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.245: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.245: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.245: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.245: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.245: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.245: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.246: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.246: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.246: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.246: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.246: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.246: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.246: Partial capture successful. Please touch the sensor again (3/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.246: Device reported enroll progress, reported 3 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.246: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.247: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.247: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.247: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.247: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.248: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.248: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.248: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.248: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.248: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.248: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.248: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.249: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.249: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.249: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.249: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.249: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.249: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.250: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.250: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.250: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.250: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.250: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.250: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.250: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.251: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Partial capture successful. Please touch the sensor again (4/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.251: Device reported enroll progress, reported 4 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.251: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.251: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.251: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.256: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.257: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.257: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.257: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.257: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.257: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.257: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.257: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.258: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.258: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.258: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.258: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.258: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.258: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.259: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.259: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.259: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.259: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.259: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.259: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.260: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.261: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Partial capture successful. Please touch the sensor again (5/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.261: Device reported enroll progress, reported 5 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.261: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.261: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.261: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.261: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.262: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.262: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.262: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.262: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.262: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.262: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.262: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.263: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.264: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.264: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.264: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.264: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.264: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.265: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.265: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.265: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.265: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.265: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.265: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.266: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.267: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Partial capture successful. Please touch the sensor again (6/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.267: Device reported enroll progress, reported 6 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.267: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.267: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.267: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.268: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.269: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.269: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.269: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.269: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.269: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.269: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.269: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.269: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.270: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.270: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.270: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.270: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.270: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.270: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.271: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.271: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.271: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.271: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.271: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.271: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.272: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.273: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Partial capture successful. Please touch the sensor again (7/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.273: Device reported enroll progress, reported 7 of 20 have been completed 152s listing - device should have prints 152s clear device storage 152s clear done 152s listing - device should be empty 152s enrolling 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 1, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 2, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 3, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 4, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 5, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 6, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 7, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 8, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 9, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 10, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 11, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 12, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 13, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 14, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 15, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 16, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 17, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 18, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 19, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 20, , None, None) 152s enroll done 152s listing - device should have 1 print 152s verifying 152s verify done 152s async identifying 152s indentification_done: 152s try to enroll duplicate 152s duplicate enroll attempt done 152s listing - device should still only have 1 print 152s enroll new finger 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 1, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 2, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 3, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 4, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 5, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 6, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 7, , None, None)(process:3066): libfprint-SSM-DEBUG: 05:37:57.273: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.273: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.273: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.273: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.274: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.274: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.274: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.274: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.274: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.274: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.274: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.275: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.280: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.280: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.280: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.280: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.280: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.281: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.281: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.281: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.281: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.281: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.281: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.282: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.283: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Response suffix valid: NO 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Response suffix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.283: Device reported enroll progress, reported 7 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.283: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.283: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.283: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.283: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.284: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.284: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.284: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.284: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.284: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.284: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.284: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.285: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.286: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.286: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.286: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.286: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.286: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.286: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.287: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.287: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.287: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.287: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.287: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.287: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.288: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.289: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Partial capture successful. Please touch the sensor again (8/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.289: Device reported enroll progress, reported 8 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.289: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.289: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.289: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.290: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.291: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.291: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.291: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.291: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.291: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.291: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.291: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.292: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.292: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.292: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.292: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.292: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.292: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.293: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.293: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.293: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.293: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.293: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.293: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.294: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.294: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.294: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.294: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.294: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.294: Response suffix valid: NO 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.294: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.294: Response suffix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.294: Device reported enroll progress, reported 8 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.294: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.295: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.295: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.295: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.296: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.296: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.296: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.296: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.296: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.296: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.296: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.296: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.297: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.298: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.298: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.298: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.298: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.298: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.298: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.298: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.298: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.298: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.298: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.298: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.299: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.300: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Partial capture successful. Please touch the sensor again (9/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.300: Device reported enroll progress, reported 9 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.300: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.300: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.300: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.300: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.301: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.301: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.301: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.301: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.301: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.301: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.301: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.302: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.302: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.302: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.302: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.302: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.302: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.302: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.303: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.303: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.303: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.303: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.303: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.303: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.304: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.305: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Partial capture successful. Please touch the sensor again (10/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.305: Device reported enroll progress, reported 10 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.305: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.305: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.305: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.305: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.306: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.306: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.306: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.306: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.306: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.306: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.306: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.307: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.307: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.307: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.307: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.307: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.307: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.308: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.308: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.308: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.308: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.308: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.308: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.312: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.312: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.312: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.312: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.312: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.312: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.312: Partial capture successful. Please touch the sensor again (11/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.312: Device reported enroll progress, reported 11 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.313: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.313: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.313: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.313: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.313: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.314: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.314: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.314: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.314: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.314: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.314: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.314: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.314: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.315: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.315: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.315: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.315: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.315: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.315: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.316: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.316: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.316: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.316: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.316: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.316: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.316: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.317: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Partial capture successful. Please touch the sensor again (12/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.317: Device reported enroll progress, reported 12 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.317: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.317: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.317: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.318: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.318: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.318: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.318: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.318: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.318: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.318: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.318: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.319: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.320: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.320: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.320: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.320: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.320: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.320: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.320: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.320: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.320: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.320: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.320: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.321: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.322: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Partial capture successful. Please touch the sensor again (13/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.322: Device reported enroll progress, reported 13 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.322: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.322: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.322: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.322: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.323: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.323: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.323: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.323: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.323: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.323: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.323: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.324: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.325: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.325: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.325: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.325: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.325: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.325: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.325: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.325: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.325: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.325: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.325: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.326: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.327: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Partial capture successful. Please touch the sensor again (14/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.327: Device reported enroll progress, reported 14 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.327: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.327: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.327: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.328: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.331: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.331: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.331: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.331: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.331: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.331: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.331: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.332: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.333: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.333: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.333: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.333: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.333: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.333: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.333: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.333: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.333: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.333: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.333: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.334: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.335: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Partial capture successful. Please touch the sensor again (15/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.335: Device reported enroll progress, reported 15 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.335: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.335: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.335: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.335: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.336: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.336: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.336: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.336: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.336: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.336: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.336: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.337: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.338: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.338: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.338: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.338: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.338: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.338: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.338: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.338: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.338: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.338: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.338: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.339: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.340: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Partial capture successful. Please touch the sensor again (16/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.340: Device reported enroll progress, reported 16 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.340: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.340: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.340: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.340: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.341: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.341: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.341: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.341: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.341: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.341: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.341: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.342: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.343: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.343: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.343: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.343: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.343: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.343: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.343: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.343: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.343: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.343: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.343: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.344: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.345: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Partial capture successful. Please touch the sensor again (17/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.345: Device reported enroll progress, reported 17 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.345: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.345: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.345: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.345: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.346: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.346: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.346: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.346: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.346: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.346: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.346: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.347: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.347: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.347: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.347: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.347: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.347: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.347: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.348: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.348: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.348: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.348: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.348: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.348: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.349: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.349: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Partial capture successful. Please touch the sensor again (18/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.349: Device reported enroll progress, reported 18 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.349: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.349: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.349: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.350: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.350: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.350: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.350: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.350: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.350: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.350: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.351: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.351: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.352: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.352: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.352: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.352: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.352: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.352: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.352: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.352: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.352: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.352: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.353: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.353: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.353: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.354: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Partial capture successful. Please touch the sensor again (19/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.354: Device reported enroll progress, reported 19 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.354: [egismoc] ENROLL_STATES entering state 8 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.354: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.354: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.354: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.355: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.355: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.355: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.355: [egismoc] ENROLL_STATES entering state 9 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.355: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.355: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.355: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.356: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.357: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.357: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.357: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.357: [egismoc] ENROLL_STATES entering state 10 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.357: Wait for finger on sensor 152s (process:3066): libfprint-device-DEBUG: 05:37:57.357: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.357: Finger on sensor callback 152s (process:3066): libfprint-device-DEBUG: 05:37:57.357: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.357: [egismoc] ENROLL_STATES entering state 11 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.357: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.357: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.357: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.358: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.359: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Read capture callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Response prefix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Response suffix valid: yes 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Partial capture successful. Please touch the sensor again (20/20) 152s (process:3066): libfprint-device-DEBUG: 05:37:57.359: Device reported enroll progress, reported 20 of 20 have been completed 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.359: [egismoc] ENROLL_STATES entering state 12 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.359: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.359: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.360: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.361: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.361: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.361: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.361: [egismoc] ENROLL_STATES entering state 13 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.361: New fingerprint ID: FP1-00000000-7-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.361: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.361: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.361: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.362: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.362: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.362: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.362: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.362: [egismoc] ENROLL_STATES entering state 14 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.362: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.362: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.362: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.363: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.364: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: Task SSM next state callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.364: [egismoc] ENROLL_STATES entering state 15 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: Enrollment was successful! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.364: Device reported enroll completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.364: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:3066): libfprint-device-DEBUG: 05:37:57.364: Print for finger FP_FINGER_RIGHT_INDEX enrolled 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.364: [egismoc] ENROLL_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.364: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.364: Updated temperature model after 0.15 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.364: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.364: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.364: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.365: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.365: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.365: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.365: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.365: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.365: Device fingerprint 2: FP1-00000000-7-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.365: Number of currently enrolled fingerprints on the device is 2 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.365: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.365: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.365: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.365: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.365: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.365: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.366: Delete 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.366: [egismoc] DELETE_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.366: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.366: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.366: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.366: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.367: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Device fingerprint 1: FP1-00000000-2-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Device fingerprint 2: FP1-00000000-7-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Number of currently enrolled fingerprints on the device is 2 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.367: [egismoc] DELETE_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Get delete command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.367: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.367: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.368: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.368: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.368: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.368: Delete callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.369: Response prefix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.369: Device reported deletion completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.369: [egismoc] DELETE_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.369: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.369: Completing action FPI_DEVICE_ACTION_DELETE in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.369: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.369: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.369: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.369: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.369: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.369: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.369: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.370: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Device fingerprint 1: FP1-00000000-7-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.370: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.370: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.370: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.370: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.370: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Clear storage 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.370: [egismoc] DELETE_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.370: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.370: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.371: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.372: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: Device fingerprint 1: FP1-00000000-7-00000000-nobody 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: Number of currently enrolled fingerprints on the device is 1 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.372: [egismoc] DELETE_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: Get delete command 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.372: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.372: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.372: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.373: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: Delete callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: Response prefix valid: yes 152s (process:3066): libfprint-device-DEBUG: 05:37:57.373: Device reported deletion completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.373: [egismoc] DELETE_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.373: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.373: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: List 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.373: [egismoc] LIST_STATES entering state 0 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: Execute command and get response 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.373: Get check bytes 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.373: [egismoc] CMD_STATES entering state 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.374: [egismoc] CMD_STATES entering state 1 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.375: Command receive callback 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.375: [egismoc] CMD_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.375: List callback 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.375: Number of currently enrolled fingerprints on the device is 0 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.375: [egismoc] LIST_STATES entering state 1 152s (process:3066): libfprint-device-DEBUG: 05:37:57.375: Device reported listing completion 152s (process:3066): libfprint-SSM-DEBUG: 05:37:57.375: [egismoc] LIST_STATES completed successfully 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.375: Task SSM done 152s (process:3066): libfprint-device-DEBUG: 05:37:57.375: Completing action FPI_DEVICE_ACTION_LIST in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.375: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.375: Closing device 152s (process:3066): libfprint-egismoc-DEBUG: 05:37:57.375: Cancel 152s (process:3066): libfprint-device-DEBUG: 05:37:57.375: Device reported close completion 152s (process:3066): libfprint-device-DEBUG: 05:37:57.375: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 152s (process:3066): libfprint-device-DEBUG: 05:37:57.375: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 152s 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 8, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 9, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 10, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 11, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 12, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 13, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 14, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 15, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 16, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 17, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 18, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 19, , None, None) 152s finger status: 152s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x69a65fb0e080 (FpiDeviceEgisMoc at 0x3b476230)>, 20, , None, None) 152s enroll new finger done 152s listing - device should have 2 prints 152s deleting first print 152s delete done 152s listing - device should only have second print 152s clear device storage 152s clear done 152s listing - device should be empty 152s ** (umockdev-run:3062): DEBUG: 05:37:57.396: umockdev.vala:154: Removing test bed /tmp/umockdev.FFQ712 152s (umockdev-run:3062): GLib-DEBUG: 05:37:57.403: unsetenv() is not thread-safe and should not be used after threads are created 152s PASS: libfprint-2/driver-egismoc-0587.test 152s Running test: libfprint-2/fpi-assembling.test 152s TAP version 14 152s # random seed: R02Sc930a33bab642bf52ced57dadf5a96a3 152s 1..1 152s # Start of assembling tests 152s # libfprint-assembling-DEBUG: calc delta completed in 0.099693 secs 152s # libfprint-assembling-DEBUG: calc delta completed in 0.089167 secs 152s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 152s # libfprint-assembling-DEBUG: calc delta completed in 0.084390 secs 152s # libfprint-assembling-DEBUG: height is 310 152s ok 1 /assembling/frames 152s # End of assembling tests 152s PASS: libfprint-2/fpi-assembling.test 152s Running test: libfprint-2/driver-upektc_img.test 152s ** (umockdev-run:3076): DEBUG: 05:37:57.744: umockdev.vala:127: Created udev test bed /tmp/umockdev.FKT212 152s ** (umockdev-run:3076): DEBUG: 05:37:57.745: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 152s ** (umockdev-run:3076): DEBUG: 05:37:57.751: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 152s ** (umockdev-run:3076): DEBUG: 05:37:57.759: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FKT212/dev/bus/usb/001/003 152s ** (umockdev-run:3076): DEBUG: 05:37:57.760: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 152s ** (umockdev-run:3076): DEBUG: 05:37:57.764: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 152s ** (umockdev-run:3076): DEBUG: 05:37:57.769: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FKT212/dev/bus/usb/001/002 152s ** (umockdev-run:3076): DEBUG: 05:37:57.769: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 152s ** (umockdev-run:3076): DEBUG: 05:37:57.772: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 152s ** (umockdev-run:3076): DEBUG: 05:37:57.778: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.FKT212/dev/bus/usb/001/001 152s ** (umockdev-run:3076): DEBUG: 05:37:57.778: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 152s ** (umockdev-run:3076): DEBUG: 05:37:57.779: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 152s (process:3080): libfprint-context-DEBUG: 05:37:57.881: Initializing FpContext (libfprint version 1.94.9+tod1) 152s (process:3080): libfprint-tod-DEBUG: 05:37:57.881: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 152s (process:3080): libfprint-context-DEBUG: 05:37:57.884: No driver found for USB device 8087:0020 152s (process:3080): libfprint-context-DEBUG: 05:37:57.884: No driver found for USB device 1D6B:0002 152s (process:3080): libfprint-device-DEBUG: 05:37:57.885: Device reported probe completion 152s (process:3080): libfprint-device-DEBUG: 05:37:57.885: Completing action FPI_DEVICE_ACTION_PROBE in idle! 152s (process:3080): libfprint-device-DEBUG: 05:37:57.885: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.887: Image device open completed 152s (process:3080): libfprint-device-DEBUG: 05:37:57.887: Device reported open completion 152s (process:3080): libfprint-device-DEBUG: 05:37:57.887: Completing action FPI_DEVICE_ACTION_OPEN in idle! 152s (process:3080): libfprint-device-DEBUG: 05:37:57.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3080): libfprint-device-DEBUG: 05:37:57.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.887: Activating image device 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.887: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.887: [upektc_img] ACTIVATE_NUM_STATES entering state 0 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.888: [upektc_img] ACTIVATE_NUM_STATES entering state 1 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.888: [upektc_img] ACTIVATE_NUM_STATES entering state 2 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.889: [upektc_img] ACTIVATE_NUM_STATES entering state 3 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.889: [upektc_img] ACTIVATE_NUM_STATES entering state 4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.890: [upektc_img] ACTIVATE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.890: [upektc_img] ACTIVATE_NUM_STATES entering state 6 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.891: [upektc_img] ACTIVATE_NUM_STATES entering state 7 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.891: [upektc_img] ACTIVATE_NUM_STATES entering state 8 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.892: [upektc_img] ACTIVATE_NUM_STATES entering state 9 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.893: [upektc_img] ACTIVATE_NUM_STATES entering state 10 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.893: [upektc_img] ACTIVATE_NUM_STATES entering state 11 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.894: Sensor type : TCS4x, width x height: 192 x 512 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.894: [upektc_img] ACTIVATE_NUM_STATES completed successfully 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.894: Image device activation completed 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 152s (process:3080): libfprint-device-DEBUG: 05:37:57.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.894: [upektc_img] CAPTURE_NUM_STATES entering state 0 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.894: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.895: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.895: 18th byte is 0c 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.895: [upektc_img] CAPTURE_NUM_STATES entering state 3 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.896: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.896: request completed, len: 0040 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.896: [upektc_img] CAPTURE_NUM_STATES entering state 4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.897: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.897: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.897: 18th byte is 00 152s (process:3080): libfprint-device-DEBUG: 05:37:57.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.898: [upektc_img] CAPTURE_NUM_STATES entering state 3 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.898: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.899: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.899: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.899: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.899: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.899: request completed, len: 07c4 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.899: Image device reported finger status: on 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.899: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.899: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.900: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.901: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.901: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.901: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.901: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.901: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.901: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.902: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.902: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.902: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.903: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.903: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.903: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.903: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.904: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.905: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.905: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.905: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.905: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.905: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.905: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.906: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.907: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.907: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.907: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.907: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.907: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.907: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.908: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.908: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.908: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.908: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.908: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.909: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.909: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.910: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.910: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.910: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.910: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.910: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.911: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.911: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.911: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.912: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.912: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.912: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.912: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.913: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.913: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.913: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.914: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.914: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.914: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.914: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.914: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.914: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.915: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.915: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.915: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.915: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.915: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.916: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.916: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.916: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.917: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.917: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.917: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.917: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.918: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.918: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.918: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.919: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.919: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.919: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.919: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.919: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.919: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.920: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.920: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.920: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.920: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.920: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.921: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.921: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.922: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.922: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.922: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.922: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.922: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.923: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.923: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.923: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.924: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.924: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.924: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.924: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.925: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.925: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.925: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.926: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.926: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.926: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.926: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.926: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.926: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.927: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.927: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.927: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.927: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.927: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.928: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.928: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.929: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.929: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.929: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.929: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.929: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.930: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.930: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.930: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.931: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.931: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.931: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.931: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.932: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.932: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.932: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.933: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.933: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.933: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.933: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.933: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.933: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.934: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.934: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.934: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.934: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.934: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.935: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.935: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.936: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.937: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.937: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.937: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.937: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.937: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.937: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.938: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.939: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.939: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.939: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.939: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.939: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.939: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.940: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.941: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.941: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.941: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.941: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.941: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.942: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.942: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.943: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.943: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.943: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.943: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.943: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.943: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.944: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.945: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.945: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.945: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.945: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.945: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.945: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.946: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.947: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.947: response_size is 2052, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.947: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.947: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.948: request completed, len: 07c4 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.948: [upektc_img] CAPTURE_NUM_STATES entering state 5 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.948: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.949: request completed, len: 0040 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.949: response_size is 186, actual_length is 64 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.949: Waiting for rest of transfer 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.949: [upektc_img] CAPTURE_NUM_STATES entering state 1 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.949: request completed, len: 007a 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.949: Image size is 55296 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.949: Image device captured an image 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.950: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 152s (process:3080): libfprint-device-DEBUG: 05:37:57.950: Device reported finger status change: FP_FINGER_STATUS_PRESENT 152s (process:3080): libfprint-device-DEBUG: 05:37:57.950: Device reported finger status change: FP_FINGER_STATUS_NONE 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.950: Image device reported finger status: off 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.950: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.950: Deactivating image device 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.950: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.950: [upektc_img] CAPTURE_NUM_STATES completed successfully 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.950: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.950: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 152s (process:3080): libfprint-SSM-DEBUG: 05:37:57.951: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 152s (process:3080): libfprint-upektc_img-DEBUG: 05:37:57.951: Deactivate completed 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.951: Image device deactivation completed 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.951: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 152s (process:3080): libfprint-image-DEBUG: 05:37:57.962: Minutiae scan completed in 0.011898 secs 152s (process:3080): libfprint-device-DEBUG: 05:37:57.962: Device reported capture completion 152s (process:3080): libfprint-device-DEBUG: 05:37:57.962: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 152s (process:3080): libfprint-device-DEBUG: 05:37:57.962: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 152s (process:3080): libfprint-image_device-DEBUG: 05:37:57.963: Image device close completed 152s (process:3080): libfprint-device-DEBUG: 05:37:57.963: Device reported close completion 152s (process:3080): libfprint-device-DEBUG: 05:37:57.963: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 152s (process:3080): libfprint-device-DEBUG: 05:37:57.963: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 153s ** (umockdev-run:3076): DEBUG: 05:37:58.075: umockdev.vala:154: Removing test bed /tmp/umockdev.FKT212 153s (umockdev-run:3076): GLib-DEBUG: 05:37:58.085: unsetenv() is not thread-safe and should not be used after threads are created 153s Comparing PNGs /tmp/libfprint-umockdev-test-1mz11d9j/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 153s PASS: libfprint-2/driver-upektc_img.test 153s Running test: libfprint-2/fpi-ssm.test 153s TAP version 14 153s # random seed: R02S0464ee0fc9cb6951a49c9b7b97ad2bed 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 Executing: libfprint-2/fpi-ssm.test 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 154s ok 35 /ssm/delayed/mark_completed/not_started 154s # End of mark_completed tests 154s # Start of cancel tests 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 154s ok 36 /ssm/delayed/cancel/error 154s # End of cancel tests 154s # End of delayed tests 154s # Start of subssm tests 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 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 37 /ssm/subssm/start 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 154s # 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. 154s # 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. 154s # 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. 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 154s ok 38 /ssm/subssm/mark_failed 154s # Start of start tests 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 154s # 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 39 /ssm/subssm/start/with_started 154s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 154s # 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-fpi-device-tod-fake_test_dev_tod_current.test 154s TAP version 14 154s # random seed: R02S80bdb534a1b1e79d49d89bbdb26753b6 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_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 4 /driver/is_open 154s ok 5 /driver/get_nr_enroll_stages 154s ok 6 /driver/set_nr_enroll_stages 154s ok 7 /driver/supports_identify 154s ok 8 /driver/supports_capture 154s ok 9 /driver/has_storage 154s ok 10 /driver/do_not_support_identify 154s ok 11 /driver/do_not_support_capture 154s ok 12 /driver/has_not_storage 154s ok 13 /driver/get_usb_device 154s ok 14 /driver/get_virtual_env 154s ok 15 /driver/get_driver_data 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s ok 16 /driver/initial_features 154s # libfprint-fake_test_dev_tod_current-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_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 18 /driver/open 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 19 /driver/close 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 20 /driver/enroll 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 21 /driver/verify 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 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_WARM -> FP_TEMPERATURE_WARM 154s ok 22 /driver/identify 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 154s # 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_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_WARM -> FP_TEMPERATURE_WARM 154s ok 23 /driver/capture 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_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 154s # 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_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 24 /driver/list 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_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_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 25 /driver/delete 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-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_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 26 /driver/clear_storage 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-device-DEBUG: Idle cancelling on ongoing operation! 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-fake_test_dev_tod_current-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_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 27 /driver/cancel 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-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-fake_test_dev_tod_current-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_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_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-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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 41 /driver/features/probe_updates 154s # End of features tests 154s # Start of initial_features tests 154s ok 42 /driver/initial_features/none 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s ok 43 /driver/initial_features/no_capture 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s ok 44 /driver/initial_features/no_verify 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s ok 45 /driver/initial_features/no_identify 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s ok 46 /driver/initial_features/no_storage 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 154s ok 47 /driver/initial_features/no_list 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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_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 ok 52 /driver/open/error 154s # End of open tests 154s # Start of close tests 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 53 /driver/close/error 154s # End of close tests 154s # Start of enroll tests 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 54 /driver/enroll/error 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-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 2096924686 of 2040458619 have been completed 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 2091729029 of 2040458619 have been completed 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 2106679763 of 2040458619 have been completed 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 55 /driver/enroll/progress 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 56 /driver/enroll/update_nbis 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 57 /driver/enroll/update_nbis_wrong_device 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 58 /driver/enroll/update_nbis_wrong_driver 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 59 /driver/enroll/update_nbis_missing_feature 154s # Start of error tests 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-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_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_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_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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 61 /driver/verify/fail 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 62 /driver/verify/retry 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 63 /driver/verify/error 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 64 /driver/verify/not_supported 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-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 65 /driver/verify/report_no_cb 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-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 66 /driver/verify/not_reported 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-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_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_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_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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_COLD 154s ok 68 /driver/identify/fail 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 69 /driver/identify/retry 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-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_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 70 /driver/identify/error 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-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_WARM -> FP_TEMPERATURE_COLD 154s ok 71 /driver/identify/not_reported 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-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 72 /driver/identify/complete_retry 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-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 73 /driver/identify/report_no_cb 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev_tod_current-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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 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_WARM -> FP_TEMPERATURE_WARM 154s ok 74 /driver/identify/suspend_continues 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev_tod_current-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.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 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_WARM -> FP_TEMPERATURE_WARM 154s ok 75 /driver/identify/suspend_succeeds 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-fake_test_dev_tod_current-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_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_WARM -> FP_TEMPERATURE_WARM 154s ok 76 /driver/identify/suspend_busy_error 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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 77 /driver/identify/suspend_while_idle 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 154s # libfprint-device-DEBUG: Tod version info is 'current' 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-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 # 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_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 156s # 156s # libfprint-fake_test_dev_tod_current-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 Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 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 # 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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.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.30 secs 161s # End of identify tests 161s # Start of capture tests 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 79 /driver/capture/not_supported 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-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_tod_current-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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_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_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 81 /driver/list/error 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 82 /driver/list/no_storage 161s # End of list tests 161s # Start of delete tests 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 83 /driver/delete/error 161s # End of delete tests 161s # Start of clear_storage tests 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 161s # libfprint-device-DEBUG: Tod version info is 'current' 161s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 84 /driver/clear_storage/error 161s # End of clear_storage tests 161s # Start of cancel tests 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 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: Getting TOD version for driver 'fake_test_dev_tod_current' 161s # libfprint-device-DEBUG: Tod version info is 'current' 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 90 /driver/action_is_cancelled/open 161s ok 91 /driver/action_is_cancelled/error 161s # Start of open tests 161s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 161s # libfprint-device-DEBUG: Tod version info is 'current' 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s ok 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_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported 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_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-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_tod_current-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_tod_current-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_tod_current-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_tod_current-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_tod_current-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_tod_current-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-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 161s # libfprint-device-DEBUG: Tod version info is 'current' 161s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported 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_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 161s # 161s # libfprint-device-DEBUG: Device reported open completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 161s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_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_tod_current-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_tod_current-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_tod_current-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_tod_current-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_tod_current-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_tod_current-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-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 161s # libfprint-device-DEBUG: Tod version info is 'current' 161s # libfprint-fake_test_dev_tod_current-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_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 161s # 161s # libfprint-device-DEBUG: Device reported close completion 161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_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/tod-fpi-device-tod-fake_test_dev_tod_current.test 161s Running test: libfprint-2/driver-realtek.test 161s ** (umockdev-run:3097): DEBUG: 05:38:06.920: umockdev.vala:127: Created udev test bed /tmp/umockdev.TP3912 161s ** (umockdev-run:3097): DEBUG: 05:38:06.921: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 161s ** (umockdev-run:3097): DEBUG: 05:38:06.922: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 161s ** (umockdev-run:3097): DEBUG: 05:38:06.927: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TP3912/dev/bus/usb/001/025 161s ** (umockdev-run:3097): DEBUG: 05:38:06.928: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 161s ** (umockdev-run:3097): DEBUG: 05:38:06.929: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 161s ** (umockdev-run:3097): DEBUG: 05:38:06.934: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TP3912/dev/bus/usb/001/001 161s ** (umockdev-run:3097): DEBUG: 05:38:06.935: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 161s ** (umockdev-run:3097): DEBUG: 05:38:06.936: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (process:3101): libfprint-context-DEBUG: 05:38:07.076: Initializing FpContext (libfprint version 1.94.9+tod1) 162s (process:3101): libfprint-tod-DEBUG: 05:38:07.076: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 162s (process:3101): libfprint-context-DEBUG: 05:38:07.080: No driver found for USB device 1D6B:0002 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.080: 107920361: ../libfprint/drivers/realtek/realtek.c:1224 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.084: Device name: Realtek USB2.0 Finger Print Bridge 162s (process:3101): libfprint-device-DEBUG: 05:38:07.085: Device reported probe completion 162s (process:3101): libfprint-device-DEBUG: 05:38:07.085: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.085: Not updating temperature model, device can run continuously! 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s libusb: error [op_handle_events] cannot find handle for fd 9 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.092: 107932057: ../libfprint/drivers/realtek/realtek.c:1269 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.094: [realtek] Init entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.095: [realtek] Init entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.095: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.096: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.096: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.097: [realtek] Init entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.097: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.097: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.097: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.098: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.099: [realtek] Init completed successfully 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.099: Init complete! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.099: Device reported open completion 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.099: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.099: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.099: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.099: 107939171: ../libfprint/drivers/realtek/realtek.c:1332 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.099: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.100: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.100: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.101: Successfully cleared storage 162s (process:3101): libfprint-device-DEBUG: 05:38:07.101: Device reported deletion completion 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.101: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.101: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.101: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.102: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.102: 107941711: ../libfprint/drivers/realtek/realtek.c:1201 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.102: [realtek] Enroll entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.102: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.106: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.107: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.108: [realtek] Enroll entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.108: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.108: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.109: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.109: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.109: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.109: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.110: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.110: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.110: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.111: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.111: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.112: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.112: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.113: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.114: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.114: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.114: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.115: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.115: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.116: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.117: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.117: Device reported enroll progress, reported 1 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.117: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.117: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.117: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.118: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.118: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.118: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.119: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.119: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.119: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.120: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.121: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.122: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.122: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.122: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.122: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.123: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.124: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.125: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.125: Device reported enroll progress, reported 2 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.125: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.125: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.125: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.125: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.126: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.126: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.127: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.127: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.128: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.128: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.130: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.131: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.131: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.131: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.131: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.132: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.133: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.134: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.134: Device reported enroll progress, reported 3 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.134: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.134: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.134: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.135: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.135: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.135: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.136: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.136: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.137: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.138: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.141: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.142: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.142: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.142: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.142: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.143: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.144: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.145: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.145: Device reported enroll progress, reported 4 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.145: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.145: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.145: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.145: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.146: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.146: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.147: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.147: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.147: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.148: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.150: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.150: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.150: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.152: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.152: Device reported enroll progress, reported 5 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.152: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.153: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.154: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.154: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.155: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.156: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.156: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.157: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.158: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.159: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.159: Device reported enroll progress, reported 6 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.159: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.159: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.160: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.162: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.162: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.163: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.163: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.164: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.165: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.165: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.165: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.166: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.166: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.167: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.168: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.168: Device reported enroll progress, reported 7 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.168: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.168: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.168: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.169: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.170: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.170: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.171: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.172: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.172: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.172: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.173: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.173: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.174: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.175: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-device-DEBUG: 05:38:07.175: Device reported enroll progress, reported 8 of 8 have been completed 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.175: [realtek] Enroll entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.175: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.176: [realtek] Enroll entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.176: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.177: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.177: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.179: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.179: [realtek] Enroll entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.179: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.179: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.181: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.181: [realtek] Enroll entering state 5 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.181: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.181: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.182: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.183: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.183: [realtek] Enroll entering state 6 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.183: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.183: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.184: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.184: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.185: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.185: [realtek] Enroll completed successfully 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.185: Enrollment complete! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.185: Device reported enroll completion 162s (process:3101): libfprint-device-DEBUG: 05:38:07.185: Print for finger FP_FINGER_UNKNOWN enrolled 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.185: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.185: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.185: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.186: 108025584: ../libfprint/drivers/realtek/realtek.c:1344 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.186: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.186: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.187: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.188: Query templates complete! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.188: Device reported listing completion 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.188: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.188: Completing action FPI_DEVICE_ACTION_LIST in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.188: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.188: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.189: 108028512: ../libfprint/drivers/realtek/realtek.c:1177 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.189: [realtek] Verify & Identify entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.189: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.189: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.190: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.191: [realtek] Verify & Identify entering state 1 162s (process:3101): libfprint-device-DEBUG: 05:38:07.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.191: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.191: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.192: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.192: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.193: [realtek] Verify & Identify entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.193: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.193: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.194: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.195: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.195: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.195: [realtek] Verify & Identify entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.195: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.196: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.196: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.197: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.197: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.197: [realtek] Verify & Identify entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.197: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.198: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.198: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.199: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.200: Device reported verify result 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.200: [realtek] Verify & Identify entering state 5 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.200: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.200: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.200: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.200: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.201: [realtek] Verify & Identify completed successfully 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.201: Verify complete! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.201: Device reported verify completion 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.201: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.201: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.201: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.202: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.202: 108041886: ../libfprint/drivers/realtek/realtek.c:1177 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.202: [realtek] Verify & Identify entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.202: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.203: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.204: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.204: [realtek] Verify & Identify entering state 1 162s (process:3101): libfprint-device-DEBUG: 05:38:07.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.204: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.205: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.205: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.205: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.206: [realtek] Verify & Identify entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.206: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.207: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.207: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.208: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.209: Device reported finger status change: FP_FINGER_STATUS_PRESENT 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.209: [realtek] Verify & Identify entering state 3 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.209: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.209: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.209: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.210: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.211: Device reported finger status change: FP_FINGER_STATUS_NONE 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.211: [realtek] Verify & Identify entering state 4 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.211: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.211: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.212: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.212: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-device-DEBUG: 05:38:07.213: Device reported identify result 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.213: [realtek] Verify & Identify completed successfully 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.213: Verify complete! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.213: Device reported identify completion 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.213: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.213: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.213: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.214: 108053933: ../libfprint/drivers/realtek/realtek.c:1313 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.214: [realtek] Delete print entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.214: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.215: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.216: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.217: [realtek] Delete print entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.217: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.217: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.218: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.218: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.219: [realtek] Delete print completed successfully 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.219: Delete print complete! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.219: Device reported deletion completion 162s (process:3101): libfprint-SSM-DEBUG: 05:38:07.219: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 162s (process:3101): libfprint-device-DEBUG: 05:38:07.219: Completing action FPI_DEVICE_ACTION_DELETE in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.219: Not updating temperature model, device can run continuously! 162s (process:3101): libfprint-realtek-DEBUG: 05:38:07.219: 108058729: ../libfprint/drivers/realtek/realtek.c:1301 162s (process:3101): libfprint-device-DEBUG: 05:38:07.219: Device reported close completion 162s (process:3101): libfprint-device-DEBUG: 05:38:07.219: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 162s (process:3101): libfprint-device-DEBUG: 05:38:07.219: Not updating temperature model, device can run continuously! 162s enrolling 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 1, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 2, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 3, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 4, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 5, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 6, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 7, None, None, None) 162s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7ceb29a2a240 (FpiDeviceRealtek at 0x3ae2dcc0)>, 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:3097): DEBUG: 05:38:07.234: umockdev.vala:154: Removing test bed /tmp/umockdev.TP3912 162s (umockdev-run:3097): GLib-DEBUG: 05:38:07.241: 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-elan.test 162s ** (umockdev-run:3109): DEBUG: 05:38:07.295: umockdev.vala:127: Created udev test bed /tmp/umockdev.YS6I22 162s ** (umockdev-run:3109): DEBUG: 05:38:07.296: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 162s ** (umockdev-run:3109): DEBUG: 05:38:07.298: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 162s ** (umockdev-run:3109): DEBUG: 05:38:07.302: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.YS6I22/dev/bus/usb/001/094 162s ** (umockdev-run:3109): DEBUG: 05:38:07.302: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 162s ** (umockdev-run:3109): DEBUG: 05:38:07.304: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 162s ** (umockdev-run:3109): DEBUG: 05:38:07.310: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.YS6I22/dev/bus/usb/001/083 162s ** (umockdev-run:3109): DEBUG: 05:38:07.310: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 162s ** (umockdev-run:3109): DEBUG: 05:38:07.312: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 162s ** (umockdev-run:3109): DEBUG: 05:38:07.316: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.YS6I22/dev/bus/usb/001/001 162s ** (umockdev-run:3109): DEBUG: 05:38:07.317: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 162s ** (umockdev-run:3109): DEBUG: 05:38:07.317: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 162s (umockdev-run:3109): GLib-GIO-DEBUG: 05:38:07.321: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 162s (process:3113): libfprint-context-DEBUG: 05:38:07.440: Initializing FpContext (libfprint version 1.94.9+tod1) 162s (process:3113): libfprint-tod-DEBUG: 05:38:07.440: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 162s (process:3113): libfprint-context-DEBUG: 05:38:07.445: No driver found for USB device 17EF:1018 162s (process:3113): libfprint-context-DEBUG: 05:38:07.445: No driver found for USB device 1D6B:0002 162s (process:3113): libfprint-device-DEBUG: 05:38:07.446: Device reported probe completion 162s (process:3113): libfprint-device-DEBUG: 05:38:07.446: Completing action FPI_DEVICE_ACTION_PROBE in idle! 162s (process:3113): libfprint-device-DEBUG: 05:38:07.446: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.449: 108288629: ../libfprint/drivers/elan.c:908 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.449: Image device open completed 162s (process:3113): libfprint-device-DEBUG: 05:38:07.449: Device reported open completion 162s (process:3113): libfprint-device-DEBUG: 05:38:07.449: Completing action FPI_DEVICE_ACTION_OPEN in idle! 162s (process:3113): libfprint-device-DEBUG: 05:38:07.449: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:3113): libfprint-device-DEBUG: 05:38:07.449: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.449: Activating image device 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.449: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.450: 108289474: ../libfprint/drivers/elan.c:960 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.450: 108289493: ../libfprint/drivers/elan.c:951 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.450: 108289503: ../libfprint/drivers/elan.c:892 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.450: 108289512: ../libfprint/drivers/elan.c:100 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.450: [elan] ACTIVATE_NUM_STATES entering state 0 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.450: 108289543: ../libfprint/drivers/elan.c:820 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.451: 108290711: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.451: 108290726: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.451: 108290736: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.452: 108291701: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.452: 108291718: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.452: [elan] ACTIVATE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.452: 108291742: ../libfprint/drivers/elan.c:820 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.452: FW ver 0x0140 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.452: [elan] ACTIVATE_NUM_STATES entering state 2 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.452: 108291775: ../libfprint/drivers/elan.c:820 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.453: 108292758: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.453: 108292798: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.453: 108292810: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293772: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293786: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.454: [elan] ACTIVATE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293802: ../libfprint/drivers/elan.c:820 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: sensor dimensions, WxH: 144x64 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.454: [elan] ACTIVATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293828: ../libfprint/drivers/elan.c:820 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293850: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.454: [elan] ACTIVATE_NUM_STATES completed successfully 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293867: ../libfprint/drivers/elan.c:881 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.454: Image device activation completed 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.454: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293898: ../libfprint/drivers/elan.c:960 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.454: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293922: ../libfprint/drivers/elan.c:960 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293929: ../libfprint/drivers/elan.c:792 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293936: ../libfprint/drivers/elan.c:100 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.454: [elan] CALIBRATE_NUM_STATES entering state 0 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.454: 108293952: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-device-DEBUG: 05:38:07.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.455: 108294933: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.455: 108294946: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.455: 108294954: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.456: 108296261: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.456: 108296300: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.456: [elan] CALIBRATE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.456: 108296328: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.456: 108296337: ../libfprint/drivers/elan.c:156 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.456: 108296348: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.456: [elan] CALIBRATE_NUM_STATES entering state 2 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.456: 108296401: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.457: 108297442: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.457: 108297459: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.457: 108297470: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.459: 108298755: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.459: 108298769: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.459: [elan] CALIBRATE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.459: 108298786: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.459: 108298792: ../libfprint/drivers/elan.c:634 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.459: calibration mean: 8421, bg mean: 5805, delta: 2616 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.459: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.459: 108298820: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.460: 108299901: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.460: 108299916: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.460: 108299926: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.461: 108301023: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.461: 108301068: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.461: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.461: 108301095: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.461: calibration status: 0x01 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.511: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.511: 108351186: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.511: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.511: 108351210: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.512: 108352113: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.512: 108352128: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.512: 108352134: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.513: 108352964: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.513: 108352974: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.513: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.513: 108352988: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.513: calibration status: 0x01 162s (process:3113): libfprint-device-DEBUG: 05:38:07.549: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.563: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.563: 108403120: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.563: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.563: 108403136: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.564: 108404299: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.564: 108404318: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.564: 108404324: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.565: 108405202: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.565: 108405216: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.565: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.565: 108405231: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.565: calibration status: 0x01 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.615: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.615: 108455389: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.615: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.615: 108455412: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.616: 108456280: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.616: 108456296: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.616: 108456303: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.617: 108457201: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.617: 108457218: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.617: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.617: 108457241: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.617: calibration status: 0x01 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.667: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.667: 108507428: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.667: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.667: 108507450: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.668: 108508097: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.668: 108508115: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.668: 108508121: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.669: 108508817: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.669: 108508827: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.669: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.669: 108508842: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.669: calibration status: 0x01 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.719: [elan] CALIBRATE_NUM_STATES entering state 6 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.719: 108559079: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.719: [elan] CALIBRATE_NUM_STATES entering state 4 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.719: 108559094: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.720: 108559947: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.720: 108559956: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.720: 108559961: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: 108560716: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: 108560731: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.721: [elan] CALIBRATE_NUM_STATES entering state 5 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: 108560747: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: calibration status: 0x03 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.721: [elan] CALIBRATE_NUM_STATES entering state 0 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: 108560762: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: 108561459: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.721: 108561468: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108561476: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108562282: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108562295: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.722: [elan] CALIBRATE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108562307: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108562311: ../libfprint/drivers/elan.c:156 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108562318: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.722: [elan] CALIBRATE_NUM_STATES entering state 2 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.722: 108562334: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.723: 108563080: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.723: 108563094: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.723: 108563103: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564061: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564087: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.724: [elan] CALIBRATE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564109: ../libfprint/drivers/elan.c:691 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564126: ../libfprint/drivers/elan.c:634 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: calibration mean: 8339, bg mean: 8146, delta: 193 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.724: [elan] CALIBRATE_NUM_STATES completed successfully 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564175: ../libfprint/drivers/elan.c:776 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564184: ../libfprint/drivers/elan.c:620 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.724: 108564196: ../libfprint/drivers/elan.c:100 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.724: [elan] CAPTURE_NUM_STATES entering state 0 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.725: 108565233: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.725: 108565253: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.725: 108565267: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.725: skipping read, not expecting anything 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.725: 108565293: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.725: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.727: 108566473: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.727: 108566491: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.727: 108566504: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.728: 108567713: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.728: 108567727: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.728: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-device-DEBUG: 05:38:07.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.728: Image device reported finger status: on 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.728: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.728: 108567814: ../libfprint/drivers/elan.c:960 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.729: 108569033: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.729: 108569070: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.729: 108569079: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.730: 108570211: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.730: 108570230: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.730: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.730: 108570252: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.730: 108570263: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.730: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.732: 108571576: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.732: 108571590: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.732: 108571600: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.733: 108572922: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.733: 108572958: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.733: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.733: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.734: 108574231: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.734: 108574246: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.734: 108574256: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.735: 108575419: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.735: 108575441: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.735: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.736: 108575473: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.736: 108575483: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.736: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.737: 108576713: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.737: 108576743: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.737: 108576752: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.738: 108577915: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.738: 108577929: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.738: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.738: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.739: 108579061: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.739: 108579075: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.739: 108579086: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.740: 108580272: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.740: 108580303: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.740: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.740: 108580327: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.740: 108580337: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.740: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.741: 108581415: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.741: 108581429: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.741: 108581441: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.743: 108582596: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.743: 108582610: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.743: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.743: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.744: 108583735: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.744: 108583748: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.744: 108583759: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.745: 108584690: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.745: 108584718: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.745: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.745: 108584736: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.745: 108584744: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.745: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.746: 108585876: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.746: 108585890: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.746: 108585901: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.747: 108587094: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.747: 108587109: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.747: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.747: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.748: 108588027: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.748: 108588050: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.748: 108588059: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.749: 108588958: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.749: 108588976: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.749: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.749: 108588996: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.749: 108589083: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.749: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.750: 108590212: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.750: 108590226: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.750: 108590237: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.751: 108591195: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.751: 108591211: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.751: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.751: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.752: 108592288: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.752: 108592315: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.752: 108592324: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108593600: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108593622: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.754: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108593635: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108593640: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.754: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108594368: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108594377: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.754: 108594382: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.755: 108595039: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.755: 108595048: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.755: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.755: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.756: 108595695: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.756: 108595704: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.756: 108595708: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108596488: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108596517: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.757: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108596528: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108596533: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.757: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108597210: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108597219: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.757: 108597223: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.758: 108597905: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.758: 108597914: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.758: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.758: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108598583: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108598591: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108598596: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108599265: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108599278: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.759: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108599288: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.759: 108599294: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.759: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.760: 108599925: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.760: 108599933: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.760: 108599939: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.761: 108600602: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.761: 108600618: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.761: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.761: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.761: 108601271: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.761: 108601279: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.761: 108601284: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.762: 108602003: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.762: 108602017: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.762: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.762: 108602026: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.762: 108602057: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.762: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.763: 108602705: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.763: 108602714: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.763: 108602719: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.763: 108603408: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.763: 108603417: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.763: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.763: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.764: 108604029: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.764: 108604044: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.764: 108604049: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108604722: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108604734: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.765: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108604744: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108604749: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.765: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108605418: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108605427: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.765: 108605431: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.766: 108606065: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.766: 108606074: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.766: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.766: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108606696: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108606704: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108606709: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108607375: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108607388: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.767: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108607398: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.767: 108607404: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.767: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.768: 108608041: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.768: 108608054: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.768: 108608058: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.769: 108608715: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.769: 108608724: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.769: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-image_device-DEBUG: 05:38:07.769: Image device reported finger status: on 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.769: 108609343: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.769: 108609362: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.769: 108609367: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.770: 108610030: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.770: 108610042: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.770: [elan] CAPTURE_NUM_STATES entering state 3 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.770: 108610052: ../libfprint/drivers/elan.c:203 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.770: 108610058: ../libfprint/drivers/elan.c:118 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.770: [elan] CAPTURE_NUM_STATES entering state 1 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108610773: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108610781: ../libfprint/drivers/elan.c:366 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108610786: ../libfprint/drivers/elan.c:379 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108611406: ../libfprint/drivers/elan.c:346 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108611415: ../libfprint/drivers/elan.c:335 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.771: [elan] CAPTURE_NUM_STATES entering state 2 162s (process:3113): libfprint-SSM-DEBUG: 05:38:07.771: [elan] CAPTURE_NUM_STATES completed successfully 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108611438: ../libfprint/drivers/elan.c:586 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108611444: ../libfprint/drivers/elan.c:315 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.771: 108611456: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.773: 108612486: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.774: 108613511: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.775: 108614601: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.776: 108615586: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.777: 108616619: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.778: 108617624: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.779: 108618634: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.780: 108619615: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-elan-DEBUG: 05:38:07.781: 108620635: ../libfprint/drivers/elan.c:272 162s (process:3113): libfprint-assembling-DEBUG: 05:38:07.897: calc delta completed in 0.115342 secs 163s (process:3113): libfprint-assembling-DEBUG: 05:38:08.027: calc delta completed in 0.129649 secs 163s (process:3113): libfprint-assembling-DEBUG: 05:38:08.027: errors: 233151 rev: 207411 163s (process:3113): libfprint-assembling-DEBUG: 05:38:08.027: height is -185 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.027: Image device captured an image 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.028: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.028: 108867679: ../libfprint/drivers/elan.c:960 163s (process:3113): libfprint-device-DEBUG: 05:38:08.028: Device reported finger status change: FP_FINGER_STATUS_PRESENT 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.028: 108867696: ../libfprint/drivers/elan.c:507 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.028: 108867702: ../libfprint/drivers/elan.c:100 163s (process:3113): libfprint-SSM-DEBUG: 05:38:08.028: [elan] STOP_CAPTURE_NUM_STATES entering state 0 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.028: 108867717: ../libfprint/drivers/elan.c:466 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108872992: ../libfprint/drivers/elan.c:346 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873039: ../libfprint/drivers/elan.c:366 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873045: ../libfprint/drivers/elan.c:379 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: skipping read, not expecting anything 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873056: ../libfprint/drivers/elan.c:335 163s (process:3113): libfprint-SSM-DEBUG: 05:38:08.033: [elan] STOP_CAPTURE_NUM_STATES completed successfully 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873069: ../libfprint/drivers/elan.c:483 163s (process:3113): libfprint-device-DEBUG: 05:38:08.033: Device reported finger status change: FP_FINGER_STATUS_NONE 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.033: Image device reported finger status: off 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873104: ../libfprint/drivers/elan.c:960 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.033: Deactivating image device 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873123: ../libfprint/drivers/elan.c:960 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873128: ../libfprint/drivers/elan.c:975 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.033: Image device deactivation completed 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.033: 108873161: ../libfprint/drivers/elan.c:960 163s (process:3113): libfprint-image-DEBUG: 05:38:08.045: Minutiae scan completed in 0.016849 secs 163s (process:3113): libfprint-device-DEBUG: 05:38:08.045: Device reported capture completion 163s (process:3113): libfprint-device-DEBUG: 05:38:08.045: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 163s (process:3113): libfprint-device-DEBUG: 05:38:08.045: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.045: 108885112: ../libfprint/drivers/elan.c:939 163s (process:3113): libfprint-elan-DEBUG: 05:38:08.045: 108885128: ../libfprint/drivers/elan.c:100 163s (process:3113): libfprint-image_device-DEBUG: 05:38:08.045: Image device close completed 163s (process:3113): libfprint-device-DEBUG: 05:38:08.045: Device reported close completion 163s (process:3113): libfprint-device-DEBUG: 05:38:08.046: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 163s (process:3113): libfprint-device-DEBUG: 05:38:08.046: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 163s ** (umockdev-run:3109): DEBUG: 05:38:08.154: umockdev.vala:154: Removing test bed /tmp/umockdev.YS6I22 163s Executing: libfprint-2/driver-elan.test 163s (umockdev-run:3109): GLib-DEBUG: 05:38:08.166: unsetenv() is not thread-safe and should not be used after threads are created 163s Comparing PNGs /tmp/libfprint-umockdev-test-r42kj9tz/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 163s PASS: libfprint-2/driver-elan.test 163s Running test: libfprint-2/driver-vfs7552.test 163s ** (umockdev-run:3122): DEBUG: 05:38:08.258: umockdev.vala:127: Created udev test bed /tmp/umockdev.A4HE22 163s ** (umockdev-run:3122): DEBUG: 05:38:08.258: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 163s ** (umockdev-run:3122): DEBUG: 05:38:08.259: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 163s ** (umockdev-run:3122): DEBUG: 05:38:08.263: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.A4HE22/dev/bus/usb/001/003 163s ** (umockdev-run:3122): DEBUG: 05:38:08.263: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 163s ** (umockdev-run:3122): DEBUG: 05:38:08.264: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 163s ** (umockdev-run:3122): DEBUG: 05:38:08.267: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.A4HE22/dev/bus/usb/001/001 163s ** (umockdev-run:3122): DEBUG: 05:38:08.267: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 163s ** (umockdev-run:3122): DEBUG: 05:38:08.267: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 163s (umockdev-run:3122): GLib-GIO-DEBUG: 05:38:08.270: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 163s (process:3126): libfprint-context-DEBUG: 05:38:08.382: Initializing FpContext (libfprint version 1.94.9+tod1) 163s (process:3126): libfprint-tod-DEBUG: 05:38:08.382: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 163s (process:3126): libfprint-context-DEBUG: 05:38:08.384: No driver found for USB device 1D6B:0002 163s (process:3126): libfprint-device-DEBUG: 05:38:08.385: Device reported probe completion 163s (process:3126): libfprint-device-DEBUG: 05:38:08.385: Completing action FPI_DEVICE_ACTION_PROBE in idle! 163s (process:3126): libfprint-device-DEBUG: 05:38:08.385: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.387: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.387: [vfs7552] DEVICE OPEN entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.387: Sending vfs7552_cmd_01 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.388: [vfs7552] DEVICE OPEN entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.388: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.389: Got 38 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.389: [vfs7552] DEVICE OPEN entering state 2 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.389: Sending vfs7552_cmd_19 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.390: [vfs7552] DEVICE OPEN entering state 3 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.390: Receiving 128 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.391: Got 68 bytes out of 128 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.391: [vfs7552] DEVICE OPEN entering state 4 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.391: Sending vfs7552_init_00 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.392: [vfs7552] DEVICE OPEN entering state 5 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.392: Receiving 64 bytes 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.393: [vfs7552] DEVICE OPEN entering state 6 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.393: Sending vfs7552_init_01 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.393: [vfs7552] DEVICE OPEN entering state 7 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.393: Receiving 64 bytes 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.394: [vfs7552] DEVICE OPEN entering state 8 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.394: Sending vfs7552_init_02 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.395: [vfs7552] DEVICE OPEN entering state 9 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.395: Receiving 64 bytes 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.396: [vfs7552] DEVICE OPEN entering state 10 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.396: Sending vfs7552_init_03 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.398: [vfs7552] DEVICE OPEN entering state 11 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.398: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.399: Got 10 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.399: [vfs7552] DEVICE OPEN entering state 12 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.399: Sending vfs7552_init_04 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.400: [vfs7552] DEVICE OPEN entering state 13 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.400: Receiving 64 bytes 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.401: [vfs7552] DEVICE OPEN completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.401: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 163s (process:3126): libfprint-image_device-DEBUG: 05:38:08.401: Image device open completed 163s (process:3126): libfprint-device-DEBUG: 05:38:08.401: Device reported open completion 163s (process:3126): libfprint-device-DEBUG: 05:38:08.401: Completing action FPI_DEVICE_ACTION_OPEN in idle! 163s (process:3126): libfprint-device-DEBUG: 05:38:08.401: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:3126): libfprint-device-DEBUG: 05:38:08.401: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 163s (process:3126): libfprint-image_device-DEBUG: 05:38:08.401: Activating image device 163s (process:3126): libfprint-image_device-DEBUG: 05:38:08.401: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 163s (process:3126): libfprint-image_device-DEBUG: 05:38:08.401: Image device activation completed 163s (process:3126): libfprint-image_device-DEBUG: 05:38:08.401: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 163s (process:3126): libfprint-image_device-DEBUG: 05:38:08.401: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 163s (process:3126): libfprint-device-DEBUG: 05:38:08.402: Device reported finger status change: FP_FINGER_STATUS_NEEDED 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.451: changing to 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.451: [vfs7552] ACTIVATE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.451: [vfs7552] ACTIVATE INIT entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.451: Sending vfs7552_image_start 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.452: [vfs7552] ACTIVATE INIT entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.452: Receiving 2048 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.453: Got 1962 bytes out of 2048 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.453: [vfs7552] ACTIVATE INIT completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.453: [vfs7552] ACTIVATE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.453: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.453: Receiving 8 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.454: Got 5 bytes out of 8 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.454: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.454: [vfs7552] ACTIVATE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.454: [vfs7552] ACTIVATE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.454: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.454: Receiving 8 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.455: Got 5 bytes out of 8 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.455: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.455: [vfs7552] ACTIVATE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.455: [vfs7552] ACTIVATE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.455: [vfs7552] ACTIVATE_NUM_STATES completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.455: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.455: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.456: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.456: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.457: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.457: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.457: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.457: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.458: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.458: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.459: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.459: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.459: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.459: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.460: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.460: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.461: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.461: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.461: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.461: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.462: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.462: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.462: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.462: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.462: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.463: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.463: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.463: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.464: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.464: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.464: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.464: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.465: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.465: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.466: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.466: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.466: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.466: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.467: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.467: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.468: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.468: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.468: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.468: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.469: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.469: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.469: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.469: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.469: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.469: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.470: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.470: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.471: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.471: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.471: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.471: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.472: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.472: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.473: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.473: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.473: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.473: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.474: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.474: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.475: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.475: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.475: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.475: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.475: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.475: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.476: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.476: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.476: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.476: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.477: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.477: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.478: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.478: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.478: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.478: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.479: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.479: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.480: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.480: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.480: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.480: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.481: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.481: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.481: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.481: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.481: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.481: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.482: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.482: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.483: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.483: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.483: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.483: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.484: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.484: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.485: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.485: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.485: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.485: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.486: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.486: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.487: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.487: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.487: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.487: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.488: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.488: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.489: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.489: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.489: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.489: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.490: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.490: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.491: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.491: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.491: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.491: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.492: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.492: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.493: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.493: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.493: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.493: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.493: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.493: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.494: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.494: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.494: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.494: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.495: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.495: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.496: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.496: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.496: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.496: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.497: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.497: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.498: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.498: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.498: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.498: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.498: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.498: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.499: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.499: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.499: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.499: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.500: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.500: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.501: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.501: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.501: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.501: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.502: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.502: Receiving 64 bytes 163s (process:3126): libfprint-device-DEBUG: 05:38:08.503: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.503: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.503: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.503: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.503: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.504: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.504: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.505: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.505: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.505: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.505: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.506: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.506: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.507: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.507: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.507: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.507: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.508: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.508: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.508: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.508: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.508: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.508: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.509: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.509: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.510: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.510: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.510: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.510: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.511: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.511: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.512: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.512: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.512: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.512: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.514: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.514: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.515: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.515: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.515: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.515: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.516: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.516: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.518: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.518: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.518: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.518: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.519: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.519: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.520: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.520: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.520: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.520: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.521: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.521: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.522: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.522: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.522: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.522: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.523: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.523: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.524: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.524: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.524: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.524: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.525: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.525: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.525: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.525: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.525: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.526: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.526: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.526: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.527: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.527: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.527: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.527: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.528: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.528: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.529: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.529: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.529: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.529: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.530: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.530: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.531: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.531: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.531: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.531: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.531: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.531: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.532: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.532: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.532: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.532: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.533: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.533: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.534: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.534: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.534: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.534: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.535: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.535: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.536: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.536: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.536: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.536: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.537: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.537: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.538: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.538: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.538: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.538: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.539: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.539: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.540: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.540: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.540: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.540: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.541: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.541: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.542: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.542: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.542: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.542: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.543: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.543: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.543: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.543: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.543: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.543: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.544: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.545: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.545: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.545: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.545: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.545: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.546: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.546: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.547: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.547: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.547: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.547: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.548: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.548: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.549: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.549: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.549: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.549: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.550: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.550: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.551: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.551: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.551: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.551: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.551: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.552: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.552: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.552: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.552: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.552: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.553: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.553: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.554: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.554: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.554: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.554: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.555: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.555: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.556: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.556: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.556: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.556: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.558: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.558: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.559: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.559: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.559: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.559: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.560: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.560: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.560: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.560: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.560: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.560: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.561: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.561: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.562: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.562: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.562: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.562: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.563: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.563: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.564: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.564: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.564: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.564: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.566: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.566: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.567: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.567: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.567: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.567: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.568: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.568: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.569: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.569: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.569: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.569: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.569: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.569: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.571: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.571: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.571: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.571: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.571: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.571: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.572: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.572: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.572: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.572: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.573: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.573: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.574: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.574: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.574: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.574: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.575: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.575: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.576: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.576: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.576: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.576: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.577: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.577: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.578: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.578: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.578: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.578: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.578: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.578: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.579: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.579: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.579: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.579: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.580: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.580: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.581: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.581: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.581: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.581: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.582: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.582: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.582: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.582: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.582: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.582: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.583: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.583: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.584: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.584: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.584: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.584: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.585: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.585: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.586: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.586: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.586: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.586: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.586: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.586: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.587: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.587: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.587: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.587: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.588: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.588: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.589: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.589: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.589: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.589: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.590: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.590: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.590: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.590: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.590: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.590: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.591: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.591: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.592: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.592: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.592: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.592: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.593: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.593: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.595: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.595: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.595: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.595: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.596: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.596: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.597: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.597: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.597: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.597: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.598: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.598: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.599: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.599: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.599: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.599: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.600: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.600: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.601: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.601: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.601: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.601: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.602: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.602: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.603: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.603: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.603: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.603: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.603: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.603: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.604: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.604: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.604: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.604: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.605: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.605: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.605: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.605: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.605: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.605: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.606: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.606: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.607: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.607: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.607: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.607: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.608: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.608: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.608: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.608: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.608: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.608: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.609: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.609: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.610: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.610: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.610: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.610: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.611: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.611: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.612: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.612: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.612: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.612: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.613: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.613: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.613: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.613: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.613: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.613: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.614: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.614: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.615: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.615: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.615: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.615: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.616: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.616: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.616: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.616: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.616: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.616: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.617: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.617: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.618: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.618: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.618: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.618: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.619: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.619: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.620: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.620: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.620: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.620: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.620: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.621: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.621: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.621: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.621: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.621: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.622: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.622: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.623: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.623: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.623: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.624: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.624: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.625: [vfs7552] CAPTURE_NUM_STATES entering state 4 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.625: variance_before = 396 163s 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.625: background stored 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.625: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.625: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.626: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.626: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.627: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.627: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.627: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.627: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.627: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.627: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.628: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.628: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.628: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.628: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.629: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.629: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.630: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.630: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.630: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.630: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.631: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.631: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.632: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.632: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.632: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.632: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.632: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.633: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.633: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.633: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.633: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.633: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.634: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.634: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.635: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.635: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.635: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.635: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.636: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.636: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.637: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.637: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.637: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.637: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.637: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.637: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.638: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.638: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.638: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.638: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.639: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.639: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.640: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.640: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.640: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.640: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.641: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.641: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.642: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.642: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.642: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.642: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.643: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.643: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.644: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.644: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.644: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.644: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.645: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.645: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.645: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.645: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.645: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.645: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.646: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.646: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.647: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.647: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.647: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.647: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.648: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.648: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.650: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.650: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.650: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.650: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.650: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.650: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.651: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.651: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.651: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.651: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.652: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.652: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.654: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.654: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.654: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.654: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.658: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.658: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.659: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.659: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.659: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.659: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.660: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.660: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.661: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.661: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.661: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.661: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.662: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.662: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.663: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.663: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.663: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.663: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.664: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.664: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.665: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.665: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.665: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.665: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.666: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.666: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.667: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.667: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.667: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.667: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.668: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.668: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.669: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.669: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.669: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.669: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.670: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.670: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.671: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.671: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.671: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.671: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.672: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.672: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.672: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.672: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.672: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.672: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.673: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.673: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.674: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.674: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.674: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.674: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.675: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.675: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.676: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.676: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.676: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.676: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.677: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.677: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.678: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.678: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.678: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.678: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.678: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.678: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.679: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.679: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.679: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.679: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.680: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.680: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.681: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.681: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.681: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.681: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.681: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.682: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.682: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.682: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.682: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.682: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.683: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.683: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.684: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.684: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.684: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.684: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.685: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.685: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.685: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.685: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.685: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.685: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.686: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.686: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.687: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.687: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.687: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.687: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.688: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.688: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.688: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.688: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.688: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.688: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.689: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.689: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.690: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.690: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.690: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.690: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.691: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.691: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.691: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.691: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.691: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.691: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.694: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.694: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.695: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.695: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.695: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.695: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.696: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.696: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.697: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.697: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.697: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.697: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.697: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.697: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.698: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.698: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.698: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.698: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.699: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.699: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.700: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.700: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.700: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.700: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.700: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.700: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.701: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.701: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.701: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.701: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.702: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.702: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.703: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.703: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.703: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.703: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.703: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.704: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.704: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.704: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.704: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.704: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.705: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.705: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.706: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.706: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.706: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.706: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.707: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.707: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.707: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.707: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.707: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.707: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.708: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.708: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.709: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.709: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.709: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.709: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.710: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.710: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.711: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.711: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.711: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.711: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.711: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.711: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.712: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.712: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.712: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.712: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.713: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.713: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.714: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.714: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.714: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.714: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.715: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.715: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.715: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.715: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.715: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.715: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.716: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.716: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.717: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.717: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.717: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.717: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.718: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.718: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.719: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.719: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.719: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.719: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.719: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.719: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.720: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.720: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.720: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.720: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.721: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.721: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.722: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.722: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.722: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.722: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.723: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.723: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.724: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.724: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.724: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.724: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.724: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.724: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.725: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.725: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.725: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.725: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.726: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.726: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.727: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.727: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.727: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.727: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.727: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.727: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.728: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.728: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.728: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.728: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.729: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.729: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.730: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.730: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.730: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.730: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.730: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.731: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.731: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.731: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.731: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.731: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.732: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.732: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.732: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.732: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.732: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.732: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.733: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.733: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.734: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.734: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.734: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.734: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.734: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.734: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.735: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.735: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.735: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.735: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.735: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.735: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.736: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.736: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.736: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.736: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.736: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.736: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.737: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.737: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.737: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.737: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.738: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.738: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.738: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.738: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.738: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.738: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.739: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.739: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.739: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.739: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.739: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.739: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.740: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.740: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.741: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.741: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.741: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.741: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.741: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.741: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.742: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.742: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.742: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.742: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.742: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.742: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.743: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.743: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.743: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.743: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.744: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.744: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.744: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.744: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.744: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.744: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.745: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.745: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.745: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.745: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.745: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.745: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.750: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.750: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.751: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.751: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.751: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.751: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.751: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.751: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.752: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.752: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.752: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.752: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.752: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.752: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.753: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.753: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.753: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.753: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.753: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.753: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.758: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.758: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.758: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.758: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.759: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.759: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.759: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.759: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.759: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.759: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.760: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.760: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.760: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.760: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.760: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.760: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.761: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.761: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.762: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.762: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.762: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.762: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.762: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.763: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.763: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.763: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.763: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.763: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.764: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.764: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.764: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.764: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.764: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.764: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.765: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.765: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.765: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.765: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.765: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.765: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.766: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.766: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.767: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.767: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.767: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.767: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.767: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.767: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.768: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.768: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.768: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.768: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.769: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.769: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.769: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.769: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.769: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.769: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.770: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.770: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.770: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.771: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.771: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.771: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.771: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.771: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.772: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.772: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.772: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.772: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.772: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.772: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.773: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.773: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.773: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.773: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.773: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.773: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.774: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.774: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.774: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.774: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.774: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.774: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.775: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.775: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.775: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.775: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.776: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.776: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.776: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.776: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.776: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.776: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.777: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.777: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.777: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.777: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.777: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.777: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.778: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.778: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.779: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.779: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.779: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.779: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.779: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.779: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.780: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.780: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.780: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.780: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.780: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.780: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.781: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.781: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.781: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.781: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.781: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.781: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.782: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.782: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.782: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.782: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.783: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.783: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.783: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.783: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.783: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.783: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.784: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.784: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.785: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.785: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.785: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.785: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.785: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.785: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.786: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.786: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.786: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.786: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.786: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.786: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.787: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.787: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.787: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.787: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.788: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.788: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.788: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.788: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.788: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.788: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.789: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.789: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.789: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.789: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.789: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.789: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.790: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.790: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.791: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.791: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.791: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.791: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.791: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.791: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.792: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.792: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.792: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.792: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.792: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.793: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.793: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.794: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.794: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.794: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.794: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.794: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.795: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.795: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.795: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.795: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.795: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.796: [vfs7552] CAPTURE_NUM_STATES entering state 4 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.796: Cleaning image 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.796: variance_after = 20 163s 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.796: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.796: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.797: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.797: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.798: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.798: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.798: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.798: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.799: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.799: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.800: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.800: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.800: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.800: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.801: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.801: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.802: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.802: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.802: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.802: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.802: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.802: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.803: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.803: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.803: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.803: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.804: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.804: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.804: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.804: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.804: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.804: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.805: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.805: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.805: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.805: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.805: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.805: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.806: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.806: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.806: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.806: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.806: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.806: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.807: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.807: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.808: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.808: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.808: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.808: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.808: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.808: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.809: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.809: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.809: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.809: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.809: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.809: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.810: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.810: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.810: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.810: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.810: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.811: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.811: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.811: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.811: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.811: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.812: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.812: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.812: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.812: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.812: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.812: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.813: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.813: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.813: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.813: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.813: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.813: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.814: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.814: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.815: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.815: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.815: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.815: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.815: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.815: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.816: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.816: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.816: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.816: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.816: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.816: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.817: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.817: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.817: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.817: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.818: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.818: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.818: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.818: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.818: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.818: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.819: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.819: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.819: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.819: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.819: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.819: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.820: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.820: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.821: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.821: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.821: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.821: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.821: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.821: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.822: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.822: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.822: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.822: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.822: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.822: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.823: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.823: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.823: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.823: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.823: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.823: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.824: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.824: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.824: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.824: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.825: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.825: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.825: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.825: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.825: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.825: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.826: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.826: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.826: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.826: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.826: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.826: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.827: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.827: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.828: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.828: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.828: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.828: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.828: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.828: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.829: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.829: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.829: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.829: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.829: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.829: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.830: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.830: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.830: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.830: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.831: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.831: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.831: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.831: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.831: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.831: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.832: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.832: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.832: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.832: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.832: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.832: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.833: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.833: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.833: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.834: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.834: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.834: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.834: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.834: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.835: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.835: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.835: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.835: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.835: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.835: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.836: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.836: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.836: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.836: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.837: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.837: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.837: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.837: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.837: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.837: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.838: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.838: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.838: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.838: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.838: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.838: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.839: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.839: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.840: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.840: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.840: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.840: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.840: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.840: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.841: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.841: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.841: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.841: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.841: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.841: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.842: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.842: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.842: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.842: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.843: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.843: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.843: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.843: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.843: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.843: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.844: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.844: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.844: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.844: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.844: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.844: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.845: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.845: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.845: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.846: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.846: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.846: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.846: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.846: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.847: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.847: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.847: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.847: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.847: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.848: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.850: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.850: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.850: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.850: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.850: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.850: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.851: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.851: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.851: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.851: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.851: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.852: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.852: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.852: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.852: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.852: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.853: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.853: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.853: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.853: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.853: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.853: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.854: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.854: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.855: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.855: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.855: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.855: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.855: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.855: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.856: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.856: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.856: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.856: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.856: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.856: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.857: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.857: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.857: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.857: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.858: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.858: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.858: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.858: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.858: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.858: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.859: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.859: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.860: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.860: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.860: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.860: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.860: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.860: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.861: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.861: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.861: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.861: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.861: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.861: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.862: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.862: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.862: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.862: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.863: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.863: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.866: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.866: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.866: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.866: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.867: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.867: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.867: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.867: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.867: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.867: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.868: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.868: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.869: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.869: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.869: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.869: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.869: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.869: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.870: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.870: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.870: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.870: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.870: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.870: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.871: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.871: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.871: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.871: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.872: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.872: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.872: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.872: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.872: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.872: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.873: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.873: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.873: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.873: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.873: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.873: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.874: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.874: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.875: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.875: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.875: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.875: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.875: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.875: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.876: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.876: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.876: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.876: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.876: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.876: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.877: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.877: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.877: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.877: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.877: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.878: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.878: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.878: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.878: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.878: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.879: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.879: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.880: [vfs7552] CAPTURE_NUM_STATES entering state 2 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.880: [vfs7552] REQUEST CHUNK entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.880: Sending vfs7552_read_image_chunk 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.880: [vfs7552] REQUEST CHUNK completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.880: [vfs7552] CAPTURE_NUM_STATES entering state 3 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.881: [vfs7552] CAPTURE_NUM_STATES entering state 4 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.881: Cleaning image 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.881: variance_after = 18 163s 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.881: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.881: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.882: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.882: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.882: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.882: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.882: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.882: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.883: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.883: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.884: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.884: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.884: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.884: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.884: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.884: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.885: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.885: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.885: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.885: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.885: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.885: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.886: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.886: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.886: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.886: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.890: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.890: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.891: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.891: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.891: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.891: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.891: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.891: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.892: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.892: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.892: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.892: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.893: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.893: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.893: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.893: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.893: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.893: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.894: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.894: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.895: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.895: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.895: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.895: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.895: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.895: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.896: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.896: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.896: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.896: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.896: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.896: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.897: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.897: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.897: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.897: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.897: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.897: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.898: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.898: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.898: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.898: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.899: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.899: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.899: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.899: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.899: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.899: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.900: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.900: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.900: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.900: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.900: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.900: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.901: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.901: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.901: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.901: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.902: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.902: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.902: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.902: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.903: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.903: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.903: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.903: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.903: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.903: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.904: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.904: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.904: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.904: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.904: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.905: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.905: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.905: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.905: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.905: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.906: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.906: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.906: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.906: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.906: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.906: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.907: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.907: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.908: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.908: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.908: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.908: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.908: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.908: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.909: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.909: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.909: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.909: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.909: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.909: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.910: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.910: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.910: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.910: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.911: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.911: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.911: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.911: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.911: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.911: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.912: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.912: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.912: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.912: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.912: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.912: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.913: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.913: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.914: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.914: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.914: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.914: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.914: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.914: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.915: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.915: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.915: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.915: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.915: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.915: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.916: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.916: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.916: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.916: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.916: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.917: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.917: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.917: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.917: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.917: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.918: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.918: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.918: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.918: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.918: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.918: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.919: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.919: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.920: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.920: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.920: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.920: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.920: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.920: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.921: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.921: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.921: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.921: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.921: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.921: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.922: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.922: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.922: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.922: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.923: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.923: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.923: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.923: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.923: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.923: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.924: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.924: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.924: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.924: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.924: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.924: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.925: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.925: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.925: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.925: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.926: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.926: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.926: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.926: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.927: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.927: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.927: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.927: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.927: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.927: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.928: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.928: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.928: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.928: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.929: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.929: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.929: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.929: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.929: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.929: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.930: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.930: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.930: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.930: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.930: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.930: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.931: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.931: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.932: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.932: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.932: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.932: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.933: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.933: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.933: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.934: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.934: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.934: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.934: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.934: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.935: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.935: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.935: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.935: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.935: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.935: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.936: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.936: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.936: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.936: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.938: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.938: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.939: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.939: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.939: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.939: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.939: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.939: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.940: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.940: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.940: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.940: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.940: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.940: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.941: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.941: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.941: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.941: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.942: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.942: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.942: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.942: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.942: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.942: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.943: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.943: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.943: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.943: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.943: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.943: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.944: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.944: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.944: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.945: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.945: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.945: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.945: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.945: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.946: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.946: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.946: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.946: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.946: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.946: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.947: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.947: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.947: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.947: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.947: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.947: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.948: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.948: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.948: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.948: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.949: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.949: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.949: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.949: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.949: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.949: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.950: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.950: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.951: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.951: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.951: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.951: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.951: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.951: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.952: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.952: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.952: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.952: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.952: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.952: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.953: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.953: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.953: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.953: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.953: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.953: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.954: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.954: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.954: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.954: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.955: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.955: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.955: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.955: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.955: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.955: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.956: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.956: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.956: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.956: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.956: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.956: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.957: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.957: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.957: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.957: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.957: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.957: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.958: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.958: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.959: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.959: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.959: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.959: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.959: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.959: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.960: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.960: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.960: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.960: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.960: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.960: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.961: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.961: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.961: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.961: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.962: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.962: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.962: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.962: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.962: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.962: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.963: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.963: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.963: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.963: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.963: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.964: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.964: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.964: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.965: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.965: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.965: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.965: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.965: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.965: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.966: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.966: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.966: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.966: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.966: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.967: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.967: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.967: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.967: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.967: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.968: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.968: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.968: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.968: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.968: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.968: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.969: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.969: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.969: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.969: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.970: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.970: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.970: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.970: Receiving 64 bytes 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.971: Got 6 bytes out of 64 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.971: [vfs7552] QUERY DATA READY completed successfully 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.971: [vfs7552] QUERY DATA READY entering state 0 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.971: Sending vfs7552_is_image_ready 163s (process:3126): libfprint-SSM-DEBUG: 05:38:08.971: [vfs7552] QUERY DATA READY entering state 1 163s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.971: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.972: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.972: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.972: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.972: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.973: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.973: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.973: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.973: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.973: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.973: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.974: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.974: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.975: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.975: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.975: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.975: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.975: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.975: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.976: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.976: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.976: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.976: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.976: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.976: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.977: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.977: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.977: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.977: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.977: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.978: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.978: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.978: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.978: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.978: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.979: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.979: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.980: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.980: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.980: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.980: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.981: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.981: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.982: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.982: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.982: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.982: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.982: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.982: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.983: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.983: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.983: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.983: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.984: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.984: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.984: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.984: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.984: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.984: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.985: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.985: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.985: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.986: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.986: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.986: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.986: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.986: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.987: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.987: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.987: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.987: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.987: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.987: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.988: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.988: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.988: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.988: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.988: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.988: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.989: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.989: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.989: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.989: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.990: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.990: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.990: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.990: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.990: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.990: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.991: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.991: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.991: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.992: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.992: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.992: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.992: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.992: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.993: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.993: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.993: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.993: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.993: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.993: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.994: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.994: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.994: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.994: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.995: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.995: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.995: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.995: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.995: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.995: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.996: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.996: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.997: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.997: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.997: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.997: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.997: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.997: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.998: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.998: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.998: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.998: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.998: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.998: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.999: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.999: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.999: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:08.999: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:08.999: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.000: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.000: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.000: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.000: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.000: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.001: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.001: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.001: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.001: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.001: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.001: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.002: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.002: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.002: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.002: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.002: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.002: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.003: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.003: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.003: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.003: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.004: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.004: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.004: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.004: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.005: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.005: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.005: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.005: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.006: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.006: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.006: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.006: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.006: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.006: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.007: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.007: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.008: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.008: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.008: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.008: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.008: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.009: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.009: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.009: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.009: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.009: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.010: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.010: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.011: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.011: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.011: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.011: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.011: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.011: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.012: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.012: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.012: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.012: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.013: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.013: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.013: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.013: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.013: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.013: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.014: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.014: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.015: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.015: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.015: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.015: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.015: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.015: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.016: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.016: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.016: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.016: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.017: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.017: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.018: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.018: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.018: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.018: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.018: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.018: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.019: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.019: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.019: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.019: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.020: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.020: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.020: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.020: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.020: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.020: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.021: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.021: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.022: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.022: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.022: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.022: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.022: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.022: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.023: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.023: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.023: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.023: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.024: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.024: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.024: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.025: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.025: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.025: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.025: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.025: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.026: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.026: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.026: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.026: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.026: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.026: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.027: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.027: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.027: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.027: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.028: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.028: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.028: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.028: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.029: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.029: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.029: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.029: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.030: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.030: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.030: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.030: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.030: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.030: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.031: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.031: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.031: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.031: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.032: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.032: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.032: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.032: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.032: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.032: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.033: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.033: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.034: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.034: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.034: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.034: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.034: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.034: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.035: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.035: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.035: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.035: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.036: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.036: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.036: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.036: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.036: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.037: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.037: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.037: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.038: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.038: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.038: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.038: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.038: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.038: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.039: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.039: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.039: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.039: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.040: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.040: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.040: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.040: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.040: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.040: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.041: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.041: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.041: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.041: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.041: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.041: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.042: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.042: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.043: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.043: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.043: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.043: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.044: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.044: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.044: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.044: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.044: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.044: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.045: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.045: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.046: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.046: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.046: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.046: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.046: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.046: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.047: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.047: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.047: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.047: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.047: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.047: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.048: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.048: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.048: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.048: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.049: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.049: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.049: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.049: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.049: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.049: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.050: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.050: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.051: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.051: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.051: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.051: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.051: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.052: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.052: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.052: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.052: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.052: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.053: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.053: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.054: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.054: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.054: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.054: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.055: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.055: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.056: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.056: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.056: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.056: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.058: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.058: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.058: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.058: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.058: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.058: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.059: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.059: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.060: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.060: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.060: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.060: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.060: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.060: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.061: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.061: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.061: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.061: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.061: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.061: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.062: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.062: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.062: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.062: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.063: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.063: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.063: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.063: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.063: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.063: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.064: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.064: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.064: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.065: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.065: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.065: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.065: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.065: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.066: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.066: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.066: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.066: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.067: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.067: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.067: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.067: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.068: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.068: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.068: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.068: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.069: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.069: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.069: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.069: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.069: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.069: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.070: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.070: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.070: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.070: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.071: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.071: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.071: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.071: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.071: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.071: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.072: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.072: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.072: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.072: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.073: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.073: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.073: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.073: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.074: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.074: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.074: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.074: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.074: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.074: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.075: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.075: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.075: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.075: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.075: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.075: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.076: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.076: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.076: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.076: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.077: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.077: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.077: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.077: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.077: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.077: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.078: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.078: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.079: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.079: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.079: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.079: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.079: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.079: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.080: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.080: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.080: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.080: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.080: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.080: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.081: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.081: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.081: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.081: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.082: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.082: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.082: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.082: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.082: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.082: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.083: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.083: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.083: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.083: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.083: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.083: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.084: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.084: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.084: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.084: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.085: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.085: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.085: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.085: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.086: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.086: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.086: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.086: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.086: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.086: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.087: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.087: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.087: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.087: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.087: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.087: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.090: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.090: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.090: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.090: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.091: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.091: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.091: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.091: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.091: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.091: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.092: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.092: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.093: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.093: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.093: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.093: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.093: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.093: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.094: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.094: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.094: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.094: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.094: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.094: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.095: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.095: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.095: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.095: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.095: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.095: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.096: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.096: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.096: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.096: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.097: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.097: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.097: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.097: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.097: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.097: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.098: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.098: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.099: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.099: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.099: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.099: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.099: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.099: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.100: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.100: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.100: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.100: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.100: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.100: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.101: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.101: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.101: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.101: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.102: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.102: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.102: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.102: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.102: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.102: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.103: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.103: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.104: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.104: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.104: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.104: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.104: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.105: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.105: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.105: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.105: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.105: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.106: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.106: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.106: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.106: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.106: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.106: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.107: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.107: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.108: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.108: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.108: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.108: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.108: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.109: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.109: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.109: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.109: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.109: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.109: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.110: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.110: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.111: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.111: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.111: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.112: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.112: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.112: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.112: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.112: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.114: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.114: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.115: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.115: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.115: variance_after = 20 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.115: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.115: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.115: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.115: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.118: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.118: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.118: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.118: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.119: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.119: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.120: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.120: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.120: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.120: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.120: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.120: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.121: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.121: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.122: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.122: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.123: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.123: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.124: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.124: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.124: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.124: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.125: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.125: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.125: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.125: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.126: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.126: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.126: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.126: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.127: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.127: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.127: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.127: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.128: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.128: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.129: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.129: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.129: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.129: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.129: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.129: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.130: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.130: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.130: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.130: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.134: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.134: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.135: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.135: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.135: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.135: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.136: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.136: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.137: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.137: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.137: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.137: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.138: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.138: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.138: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.138: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.138: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.138: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.139: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.139: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.140: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.140: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.140: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.140: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.141: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.141: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.142: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.142: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.142: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.142: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.142: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.142: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.143: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.143: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.143: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.143: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.144: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.144: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.145: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.145: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.145: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.145: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.145: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.145: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.146: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.146: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.146: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.146: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.147: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.147: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.148: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.148: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.148: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.148: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.148: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.148: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.149: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.149: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.149: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.149: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.150: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.150: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.151: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.151: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.151: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.151: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.151: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.152: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.152: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.152: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.152: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.152: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.153: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.153: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.154: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.154: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.154: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.154: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.154: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.155: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.155: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.155: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.155: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.155: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.156: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.156: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.157: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.157: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.157: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.157: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.158: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.158: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.159: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.159: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.159: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.159: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.159: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.159: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.160: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.160: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.160: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.160: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.161: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.161: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.162: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.162: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.162: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.162: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.162: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.162: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.163: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.163: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.163: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.163: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.164: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.164: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.165: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.165: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.165: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.165: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.166: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.166: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.166: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.167: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.167: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.167: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.167: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.167: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.168: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.168: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.168: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.168: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.169: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.169: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.170: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.170: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.170: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.170: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.170: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.170: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.171: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.171: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.171: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.171: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.172: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.172: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.173: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.173: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.173: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.173: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.174: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.174: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.175: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.175: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.175: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.175: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.175: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.175: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.176: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.176: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.176: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.176: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.176: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.177: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.177: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.177: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.177: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.177: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.178: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.178: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.179: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.179: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.179: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.179: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.179: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.180: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.180: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.181: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.181: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.181: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.181: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.181: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.182: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.182: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.182: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.182: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.183: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.183: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.183: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.183: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.183: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.183: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.185: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.185: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.186: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.186: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.186: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.186: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.187: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.187: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.187: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.187: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.187: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.187: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.188: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.188: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.188: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.188: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.188: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.188: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.189: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.189: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.190: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.190: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.190: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.190: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.190: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.190: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.191: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.191: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.191: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.191: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.192: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.192: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.192: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.192: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.192: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.192: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.193: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.193: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.193: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.194: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.194: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.194: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.198: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.198: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.199: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.199: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.199: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.199: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.200: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.200: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.200: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.200: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.200: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.200: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.201: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.201: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.201: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.202: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.202: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.202: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.202: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.202: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.203: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.203: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.203: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.203: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.204: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.204: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.204: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.204: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.204: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.204: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.205: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.205: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.206: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.206: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.206: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.206: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.206: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.207: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.207: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.207: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.207: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.207: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.207: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.208: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.208: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.209: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.209: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.209: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.210: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.210: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.210: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.210: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.210: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.211: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.211: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.212: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.212: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.212: variance_after = 18 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.212: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.212: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.212: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.212: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.213: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.213: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.213: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.213: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.214: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.214: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.214: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.214: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.214: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.214: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.215: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.215: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.216: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.216: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.216: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.216: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.216: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.216: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.217: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.217: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.217: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.217: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.217: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.217: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.218: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.218: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.218: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.218: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.219: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.219: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.219: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.219: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.219: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.219: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.220: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.220: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.220: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.220: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.221: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.221: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.221: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.221: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.222: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.222: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.222: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.222: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.222: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.222: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.223: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.223: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.223: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.223: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.224: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.224: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.224: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.224: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.224: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.224: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.225: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.225: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.226: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.226: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.226: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.226: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.226: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.226: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.227: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.227: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.227: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.227: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.228: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.228: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.228: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.228: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.228: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.228: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.230: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.230: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.230: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.230: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.230: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.230: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.231: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.231: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.232: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.232: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.232: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.232: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.232: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.232: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.233: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.233: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.233: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.233: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.234: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.234: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.234: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.234: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.234: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.234: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.235: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.235: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.235: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.236: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.236: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.236: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.236: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.236: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.237: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.237: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.237: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.237: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.237: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.237: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.238: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.238: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.238: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.238: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.239: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.239: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.240: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.240: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.240: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.240: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.240: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.240: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.241: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.241: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.241: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.241: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.242: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.242: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.243: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.243: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.243: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.243: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.243: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.243: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.244: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.244: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.244: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.244: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.245: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.245: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.246: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.246: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.246: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.246: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.247: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.247: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.247: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.247: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.247: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.247: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.248: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.248: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.249: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.249: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.249: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.249: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.250: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.250: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.250: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.250: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.250: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.251: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.251: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.251: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.252: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.252: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.252: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.252: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.253: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.253: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.253: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.254: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.254: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.254: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.254: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.254: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.255: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.255: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.255: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.255: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.256: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.256: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.257: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.257: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.257: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.257: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.257: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.257: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.258: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.258: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.258: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.258: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.259: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.259: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.260: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.260: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.260: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.260: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.260: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.260: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.261: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.261: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.261: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.261: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.262: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.262: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.263: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.263: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.263: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.263: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.264: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.264: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.264: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.264: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.264: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.264: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.265: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.265: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.266: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.266: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.266: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.266: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.267: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.267: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.267: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.267: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.268: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.268: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.268: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.268: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.269: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.269: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.269: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.269: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.270: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.270: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.270: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.270: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.270: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.270: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.271: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.271: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.272: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.272: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.272: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.272: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.272: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.272: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.273: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.273: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.273: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.273: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.274: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.274: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.274: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.274: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.275: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.275: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.275: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.275: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.276: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.276: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.276: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.276: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.277: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.277: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.277: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.277: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.277: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.277: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.278: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.278: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.279: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.279: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.279: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.279: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.279: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.279: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.280: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.280: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.280: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.280: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.281: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.281: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.281: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.281: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.281: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.282: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.282: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.282: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.283: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.283: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.283: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.283: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.283: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.283: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.284: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.284: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.284: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.284: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.285: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.285: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.286: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.286: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.286: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.286: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.286: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.286: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.287: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.287: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.287: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.287: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.287: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.288: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.288: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.288: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.288: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.288: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.289: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.289: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.289: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.290: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.290: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.290: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.290: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.290: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.290: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.291: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.291: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.291: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.291: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.291: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.292: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.292: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.292: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.293: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.293: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.294: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.294: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.294: variance_after = 18 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.294: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.294: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.294: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.294: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.295: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.295: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.295: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.295: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.296: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.296: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.297: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.297: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.297: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.297: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.297: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.297: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.298: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.298: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.298: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.298: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.299: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.299: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.300: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.300: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.300: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.300: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.300: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.300: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.301: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.301: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.301: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.301: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.302: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.302: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.303: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.303: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.303: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.303: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.303: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.303: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.304: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.304: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.304: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.304: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.305: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.305: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.306: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.306: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.306: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.306: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.306: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.306: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.307: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.307: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.307: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.307: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.308: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.308: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.308: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.308: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.308: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.308: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.309: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.309: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.310: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.310: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.310: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.310: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.310: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.310: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.311: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.311: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.311: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.311: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.312: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.312: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.312: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.312: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.313: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.313: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.313: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.313: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.314: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.314: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.314: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.314: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.314: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.314: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.315: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.315: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.315: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.315: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.316: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.316: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.316: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.316: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.316: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.316: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.317: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.317: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.318: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.318: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.318: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.318: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.318: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.318: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.319: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.319: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.319: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.319: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.320: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.320: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.321: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.321: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.321: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.321: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.321: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.321: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.322: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.322: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.322: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.322: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.323: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.323: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.323: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.323: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.323: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.323: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.324: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.324: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.325: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.325: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.325: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.325: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.325: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.325: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.326: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.326: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.326: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.326: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.326: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.326: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.327: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.327: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.327: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.327: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.328: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.328: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.328: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.328: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.328: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.328: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.329: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.329: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.330: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.330: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.330: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.330: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.330: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.331: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.331: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.331: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.331: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.331: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.332: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.332: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.333: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.333: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.333: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.333: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.333: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.334: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.334: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.334: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.334: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.334: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.335: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.335: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.335: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.335: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.335: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.335: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.336: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.336: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.337: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.337: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.337: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.337: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.337: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.337: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.338: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.338: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.338: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.338: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.339: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.339: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.339: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.339: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.339: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.339: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.340: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.340: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.341: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.341: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.341: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.341: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.341: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.341: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.342: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.342: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.342: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.342: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.343: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.343: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.343: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.343: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.343: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.343: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.344: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.344: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.345: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.345: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.345: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.345: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.345: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.345: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.346: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.346: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.346: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.346: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.347: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.347: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.347: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.347: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.347: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.347: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.348: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.348: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.350: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.350: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.350: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.350: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.351: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.351: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.352: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.352: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.352: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.352: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.352: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.352: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.353: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.353: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.353: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.353: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.354: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.354: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.354: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.354: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.354: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.354: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.355: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.355: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.356: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.356: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.356: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.356: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.356: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.356: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.357: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.357: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.357: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.357: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.357: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.358: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.358: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.358: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.358: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.358: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.359: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.359: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.360: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.360: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.360: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.360: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.360: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.360: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.361: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.361: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.361: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.361: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.362: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.362: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.363: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.363: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.363: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.363: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.363: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.363: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.364: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.364: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.364: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.364: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.365: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.365: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.366: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.366: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.366: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.366: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.366: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.366: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.367: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.367: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.367: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.367: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.368: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.368: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.368: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.368: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.368: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.368: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.369: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.369: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.370: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.370: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.370: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.370: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.370: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.370: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.371: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.371: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.371: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.371: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.372: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.372: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.372: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.373: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.373: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.373: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.373: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.373: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.374: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.374: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.374: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.374: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.375: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.375: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.375: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.375: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.375: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.375: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.376: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.376: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.377: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.377: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.377: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.377: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.377: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.378: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.378: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.378: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.378: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.378: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.379: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.379: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.380: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.380: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.380: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.380: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.380: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.380: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.381: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.381: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.381: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.381: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.382: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.382: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.382: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.382: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.383: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.383: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.383: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.383: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.384: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.384: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.384: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.384: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.384: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.385: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.385: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.385: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.385: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.385: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.386: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.386: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.387: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.387: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.387: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.387: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.387: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.388: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.388: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.388: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.388: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.388: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.389: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.389: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.390: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.390: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.390: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.390: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.391: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.391: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.392: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.392: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.392: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.392: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.392: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.392: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.393: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.393: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.393: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.393: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.394: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.394: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.394: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.395: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.395: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.395: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.395: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.395: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.396: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.396: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.396: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.396: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.397: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.397: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.397: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.397: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.397: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.397: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.398: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.398: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.399: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.399: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.399: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.399: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.400: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.400: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.401: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.401: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.401: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.401: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.402: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.402: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.403: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.403: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.403: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.403: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.403: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.403: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.405: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.405: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.405: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.405: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.406: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.406: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.407: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.407: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.407: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.407: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.408: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.408: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.409: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.409: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.409: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.409: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.409: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.409: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.410: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.410: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.410: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.410: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.411: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.411: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.412: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.412: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.412: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.412: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.412: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.412: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.413: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.413: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.413: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.413: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.414: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.414: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.414: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.415: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.415: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.415: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.415: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.415: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.416: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.416: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.416: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.416: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.417: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.417: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.417: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.417: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.417: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.417: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.418: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.418: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.419: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.419: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.419: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.419: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.420: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.420: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.420: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.420: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.420: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.420: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.421: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.421: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.422: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.422: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.422: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.422: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.423: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.423: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.423: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.423: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.423: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.423: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.423: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.424: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.424: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.425: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.425: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.425: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.425: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.425: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.426: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.426: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.426: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.427: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.427: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.428: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.428: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.428: variance_after = 18 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.428: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.428: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.429: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.429: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.430: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.431: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.431: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.431: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.431: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.431: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.432: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.432: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.432: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.432: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.433: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.433: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.434: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.434: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.434: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.434: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.435: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.435: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.436: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.436: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.436: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.436: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.436: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.436: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.437: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.437: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.437: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.437: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.438: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.438: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.438: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.439: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.439: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.439: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.439: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.439: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.440: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.440: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.440: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.440: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.441: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.441: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.442: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.442: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.442: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.442: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.443: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.443: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.444: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.444: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.444: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.444: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.445: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.445: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.446: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.446: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.446: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.446: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.447: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.447: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.448: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.448: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.448: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.448: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.449: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.449: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.450: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.450: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.450: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.450: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.451: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.451: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.451: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.452: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.452: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.452: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.452: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.452: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.453: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.453: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.453: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.453: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.454: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.454: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.454: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.454: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.454: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.454: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.455: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.455: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.456: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.456: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.456: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.456: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.457: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.457: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.458: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.458: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.458: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.458: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.459: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.459: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.460: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.460: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.460: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.460: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.460: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.461: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.461: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.461: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.461: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.461: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.462: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.462: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.463: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.463: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.463: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.463: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.463: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.463: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.464: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.464: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.464: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.464: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.465: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.465: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.465: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.465: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.465: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.465: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.466: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.466: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.467: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.467: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.467: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.467: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.467: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.467: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.468: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.468: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.468: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.468: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.469: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.469: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.470: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.470: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.470: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.470: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.471: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.471: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.473: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.473: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.473: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.473: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.474: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.474: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.475: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.475: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.476: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.476: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.477: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.477: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.478: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.478: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.478: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.478: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.479: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.479: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.480: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.480: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.480: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.480: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.480: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.480: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.481: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.481: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.481: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.481: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.482: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.482: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.483: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.483: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.483: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.483: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.484: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.484: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.485: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.485: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.485: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.485: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.486: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.486: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.487: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.487: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.487: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.487: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.487: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.487: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.488: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.488: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.488: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.488: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.489: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.489: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.489: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.489: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.490: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.490: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.490: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.490: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.491: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.491: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.491: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.491: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.491: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.491: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.492: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.492: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.492: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.492: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.493: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.493: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.493: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.494: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.494: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.494: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.495: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.495: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.495: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.495: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.495: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.495: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.496: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.496: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.497: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.497: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.497: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.497: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.497: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.497: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.498: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.498: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.498: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.498: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.499: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.499: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.499: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.499: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.499: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.499: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.500: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.500: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.501: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.501: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.501: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.501: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.501: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.502: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.502: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.502: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.502: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.502: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.503: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.503: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.504: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.504: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.504: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.504: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.504: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.504: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.505: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.505: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.505: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.505: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.506: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.506: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.506: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.506: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.507: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.507: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.507: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.507: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.508: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.508: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.508: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.508: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.509: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.509: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.509: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.509: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.509: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.509: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.510: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.510: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.511: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.511: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.511: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.511: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.512: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.512: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.512: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.512: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.512: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.512: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.513: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.513: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.514: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.514: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.514: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.514: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.514: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.514: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.515: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.515: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.515: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.515: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.516: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.516: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.516: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.516: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.517: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.517: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.517: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.517: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.518: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.518: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.518: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.518: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.519: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.519: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.519: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.519: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.519: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.519: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.520: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.520: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.521: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.521: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.521: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.521: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.521: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.521: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.522: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.522: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.522: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.522: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.523: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.523: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.524: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.524: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.524: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.524: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.525: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.525: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.526: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.526: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.526: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.526: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.527: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.527: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.528: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.528: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.528: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.528: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.529: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.529: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.529: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.530: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.530: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.530: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.530: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.530: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.531: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.531: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.531: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.531: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.532: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.532: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.533: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.533: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.533: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.533: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.533: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.533: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.534: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.534: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.534: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.534: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.535: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.535: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.535: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.536: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.536: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.536: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.536: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.536: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.537: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.537: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.537: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.537: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.542: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.542: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.543: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.543: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.543: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.543: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.544: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.544: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.544: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.544: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.544: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.544: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.545: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.545: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.546: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.546: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.546: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.546: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.546: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.546: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.547: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.547: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.547: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.547: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.548: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.548: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.549: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.549: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.549: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.549: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.549: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.549: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.550: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.550: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.550: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.550: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.551: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.551: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.552: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.552: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.552: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.552: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.552: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.552: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.553: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.553: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.553: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.553: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.554: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.554: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.555: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.555: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.555: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.555: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.556: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.556: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.557: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.557: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.557: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.557: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.557: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.557: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.558: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.558: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.558: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.558: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.559: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.559: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.560: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.560: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.560: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.560: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.560: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.560: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.561: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.561: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.561: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.561: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.562: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.562: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.563: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.563: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.563: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.563: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.563: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.564: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.564: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.564: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.564: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.564: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.565: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.565: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.566: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.566: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.566: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.566: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.566: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.566: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.567: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.567: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.567: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.567: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.568: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.568: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.569: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.569: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.569: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.569: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.570: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.570: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.570: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.570: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.570: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.570: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.571: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.571: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.572: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.572: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.572: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.572: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.572: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.572: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.573: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.573: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.573: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.573: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.574: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.574: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.574: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.574: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.574: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.574: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.575: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.575: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.576: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.576: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.576: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.576: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.576: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.576: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.577: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.577: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.577: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.577: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.578: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.578: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.578: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.578: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.578: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.578: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.579: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.579: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.580: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.580: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.580: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.580: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.582: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.582: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.583: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.583: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.583: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.583: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.583: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.584: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.584: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.584: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.584: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.584: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.585: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.585: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.586: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.586: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.586: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.586: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.586: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.587: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.587: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.587: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.587: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.587: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.588: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.588: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.589: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.589: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.589: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.589: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.589: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.589: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.590: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.590: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.590: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.590: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.591: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.591: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.591: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.591: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.591: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.591: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.591: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.592: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.592: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.593: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.593: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.593: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.593: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.593: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.594: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.594: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.594: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.595: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.595: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.595: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.595: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.595: variance_after = 18 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.595: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.595: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.596: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.596: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.597: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.597: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.597: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.597: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.597: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.598: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.598: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.598: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.598: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.598: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.599: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.599: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.600: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.600: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.600: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.600: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.600: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.600: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.601: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.601: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.601: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.601: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.602: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.602: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.603: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.603: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.603: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.603: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.603: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.603: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.604: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.604: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.604: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.604: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.605: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.605: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.605: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.605: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.605: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.605: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.606: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.606: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.607: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.607: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.607: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.607: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.607: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.607: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.608: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.608: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.608: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.608: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.609: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.609: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.610: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.610: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.610: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.610: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.610: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.610: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.611: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.611: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.611: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.611: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.612: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.612: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.613: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.613: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.613: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.613: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.613: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.613: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.614: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.614: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.614: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.614: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.615: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.615: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.615: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.615: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.615: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.615: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.616: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.616: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.617: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.617: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.617: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.617: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.617: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.618: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.618: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.618: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.618: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.618: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.619: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.619: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.620: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.620: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.620: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.620: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.620: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.620: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.621: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.621: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.621: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.621: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.622: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.622: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.623: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.623: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.623: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.623: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.623: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.623: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.624: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.624: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.624: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.624: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.625: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.625: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.625: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.626: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.626: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.626: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.626: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.626: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.627: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.627: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.627: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.627: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.628: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.628: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.628: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.628: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.628: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.628: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.629: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.629: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.630: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.630: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.630: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.630: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.631: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.631: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.631: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.631: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.631: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.631: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.632: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.632: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.633: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.633: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.633: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.633: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.633: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.633: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.634: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.634: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.634: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.634: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.635: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.635: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.636: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.636: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.636: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.636: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.638: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.638: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.639: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.639: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.639: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.639: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.640: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.640: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.640: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.640: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.640: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.640: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.641: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.641: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.642: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.642: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.642: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.642: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.642: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.642: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.643: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.643: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.643: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.643: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.644: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.644: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.645: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.645: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.645: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.645: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.645: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.645: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.646: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.646: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.646: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.646: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.647: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.647: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.648: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.648: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.648: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.648: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.648: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.648: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.649: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.649: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.649: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.649: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.650: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.650: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.651: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.651: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.651: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.651: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.651: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.651: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.652: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.652: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.652: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.652: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.653: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.653: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.653: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.653: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.654: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.654: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.654: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.654: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.655: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.655: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.655: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.655: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.656: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.656: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.656: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.656: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.656: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.656: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.657: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.657: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.658: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.658: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.658: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.658: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.658: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.658: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.659: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.659: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.659: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.659: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.659: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.660: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.660: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.660: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.660: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.660: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.661: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.661: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.662: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.662: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.662: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.663: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.663: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.663: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.663: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.663: variance_after = 17 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.663: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.663: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.664: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.664: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.665: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.665: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.665: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.665: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.665: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.665: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.666: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.666: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.666: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.666: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.667: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.667: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.668: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.668: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.668: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.668: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.668: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.668: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.669: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.669: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.669: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.669: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.670: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.670: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.671: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.671: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.671: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.671: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.671: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.671: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.672: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.672: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.672: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.672: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.673: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.673: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.674: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.674: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.674: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.674: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.674: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.674: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.675: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.675: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.675: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.675: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.676: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.676: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.676: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.676: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.676: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.676: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.677: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.677: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.678: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.678: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.678: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.678: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.679: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.679: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.679: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.679: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.679: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.679: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.680: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.680: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.681: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.681: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.681: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.681: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.681: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.681: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.682: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.682: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.682: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.682: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.683: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.683: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.684: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.684: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.684: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.684: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.684: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.684: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.685: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.685: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.685: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.685: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.686: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.686: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.686: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.686: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.686: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.686: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.687: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.687: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.688: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.688: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.688: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.688: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.688: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.688: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.689: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.689: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.689: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.689: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.690: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.690: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.691: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.691: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.691: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.691: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.691: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.691: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.692: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.692: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.692: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.692: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.693: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.693: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.693: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.693: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.693: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.693: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.694: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.694: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.695: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.695: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.695: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.695: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.695: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.695: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.696: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.696: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.696: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.696: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.697: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.697: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.697: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.698: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.698: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.698: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.698: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.698: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.699: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.699: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.699: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.699: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.700: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.700: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.701: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.701: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.701: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.701: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.701: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.701: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.702: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.702: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.702: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.702: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.703: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.703: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.704: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.704: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.704: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.704: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.704: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.704: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.705: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.705: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.705: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.705: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.706: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.706: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.706: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.706: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.707: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.707: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.707: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.707: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.708: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.708: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.708: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.708: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.710: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.710: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.711: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.711: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.711: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.711: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.712: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.712: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.712: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.713: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.713: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.713: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.713: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.713: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.714: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.714: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.714: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.714: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.715: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.715: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.716: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.716: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.716: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.716: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.716: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.716: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.717: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.717: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.717: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.717: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.718: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.718: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.718: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.718: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.719: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.719: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.719: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.719: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.720: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.720: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.720: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.720: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.721: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.721: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.722: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.722: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.722: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.722: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.723: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.723: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.724: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.724: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.724: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.724: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.724: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.724: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.725: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.725: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.725: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.725: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.726: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.726: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.726: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.726: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.726: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.726: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.727: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.727: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.728: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.728: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.728: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.728: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.728: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.729: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.729: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.729: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.730: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.730: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.731: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.731: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.731: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.732: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.732: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.733: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.733: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.733: variance_after = 16 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.733: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.733: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.734: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.734: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.735: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.735: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.735: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.735: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.736: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.736: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.737: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.737: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.737: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.737: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.738: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.738: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.739: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.739: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.739: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.739: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.740: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.740: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.741: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.741: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.741: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.741: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.741: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.741: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.742: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.742: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.742: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.742: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.743: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.743: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.744: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.744: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.744: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.744: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.746: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.746: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.747: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.747: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.747: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.747: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.748: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.748: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.749: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.749: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.749: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.749: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.749: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.749: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.750: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.750: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.750: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.750: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.751: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.751: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.751: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.751: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.751: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.751: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.752: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.752: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.753: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.753: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.753: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.753: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.754: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.754: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.754: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.754: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.754: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.754: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.755: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.755: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.756: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.756: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.756: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.756: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.756: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.756: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.757: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.757: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.757: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.757: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.758: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.758: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.758: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.758: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.758: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.758: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.759: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.759: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.760: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.760: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.760: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.760: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.760: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.760: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.761: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.761: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.761: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.761: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.762: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.762: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.762: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.762: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.762: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.762: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.763: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.763: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.764: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.764: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.764: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.764: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.764: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.764: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.765: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.765: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.765: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.765: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.766: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.766: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.766: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.766: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.766: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.766: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.767: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.767: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.768: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.768: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.768: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.768: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.768: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.768: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.769: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.769: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.769: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.769: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.770: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.770: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.770: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.770: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.770: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.770: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.771: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.771: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.772: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.772: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.772: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.772: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.772: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.772: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.773: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.773: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.773: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.773: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.774: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.774: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.774: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.774: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.774: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.774: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.775: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.775: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.775: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.776: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.776: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.776: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.776: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.776: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.777: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.777: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.777: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.777: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.777: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.777: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.778: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.778: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.778: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.778: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.779: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.779: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.779: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.779: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.780: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.780: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.780: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.780: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.781: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.781: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.781: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.781: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.781: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.781: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.782: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.782: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.782: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.782: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.783: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.783: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.784: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.784: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.784: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.784: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.784: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.784: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.785: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.785: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.785: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.785: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.786: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.786: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.787: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.787: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.787: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.787: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.788: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.788: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.788: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.789: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.789: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.789: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.789: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.789: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.790: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.790: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.790: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.790: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.791: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.791: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.792: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.792: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.792: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.792: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.792: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.793: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.793: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.793: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.793: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.793: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.794: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.794: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.795: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.795: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.795: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.795: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.795: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.796: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.796: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.796: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.796: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.796: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.797: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.797: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.798: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.798: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.798: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.798: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.798: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.799: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.799: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.799: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.800: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.800: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.801: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.801: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.801: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.801: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.801: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.802: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.802: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.802: variance_after = 17 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.802: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.802: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.803: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.803: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.804: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.804: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.804: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.804: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.805: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.805: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.806: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.806: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.806: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.806: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.806: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.806: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.807: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.807: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.807: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.807: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.808: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.808: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.809: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.809: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.809: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.809: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.809: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.809: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.810: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.810: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.810: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.810: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.811: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.811: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.811: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.811: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.811: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.812: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.812: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.812: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.813: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.813: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.813: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.813: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.814: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.814: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.815: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.815: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.815: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.815: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.815: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.815: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.816: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.816: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.816: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.816: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.817: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.817: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.817: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.818: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.818: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.818: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.818: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.818: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.819: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.819: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.819: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.819: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.820: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.820: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.821: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.821: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.821: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.821: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.821: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.821: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.822: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.822: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.822: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.822: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.823: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.823: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.823: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.823: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.823: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.823: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.824: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.824: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.825: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.825: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.825: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.825: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.826: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.826: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.826: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.826: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.827: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.827: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.827: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.827: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.828: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.828: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.828: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.828: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.829: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.829: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.830: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.830: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.830: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.830: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.831: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.831: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.831: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.831: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.831: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.831: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.832: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.832: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.833: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.833: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.833: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.833: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.833: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.833: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.834: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.834: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.834: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.834: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.835: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.835: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.836: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.836: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.836: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.836: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.836: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.836: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.837: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.837: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.837: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.837: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.838: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.838: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.838: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.838: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.838: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.838: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.839: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.839: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.840: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.840: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.840: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.840: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.840: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.840: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.841: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.841: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.841: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.841: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.842: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.842: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.842: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.843: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.843: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.843: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.843: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.843: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.844: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.844: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.844: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.844: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.845: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.845: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.845: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.845: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.845: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.845: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.846: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.846: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.847: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.847: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.847: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.847: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.848: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.848: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.848: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.848: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.848: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.848: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.849: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.849: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.850: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.850: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.850: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.850: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.850: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.850: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.851: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.851: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.851: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.851: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.852: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.852: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.853: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.853: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.853: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.853: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.853: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.853: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.854: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.854: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.854: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.854: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.855: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.855: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.856: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.856: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.856: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.856: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.856: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.856: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.857: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.857: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.857: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.857: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.858: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.858: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.858: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.858: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.858: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.858: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.859: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.859: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.860: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.860: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.860: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.860: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.860: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.860: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.861: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.861: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.861: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.861: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.862: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.862: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.863: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.863: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.863: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.863: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.865: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.865: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.865: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.865: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.865: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.865: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.866: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.866: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.867: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.867: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.867: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.867: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.867: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.867: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.868: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.868: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.868: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.868: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.869: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.869: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.869: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.869: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.869: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.869: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.870: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.870: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.871: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.871: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.871: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.871: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.872: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.872: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.872: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.872: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.872: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.872: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.873: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.873: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.874: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.874: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.874: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.874: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.874: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.875: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.875: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.875: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.876: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.876: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.876: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.876: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.876: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.877: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.877: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.878: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.878: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.878: variance_after = 17 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.878: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.878: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.879: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.879: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.879: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.879: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.880: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.880: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.880: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.880: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.881: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.881: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.881: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.881: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.882: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.882: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.882: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.882: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.882: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.882: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.883: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.883: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.884: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.884: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.884: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.884: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.884: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.885: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.885: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.885: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.885: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.885: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.886: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.886: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.887: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.887: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.887: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.887: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.887: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.887: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.888: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.888: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.888: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.888: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.889: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.889: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.890: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.890: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.890: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.890: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.890: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.890: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.891: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.891: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.891: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.891: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.894: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.895: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.895: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.895: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.895: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.895: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.896: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.896: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.897: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.897: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.897: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.897: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.898: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.898: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.899: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.899: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.899: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.899: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.899: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.899: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.900: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.900: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.900: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.900: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.901: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.901: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.901: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.901: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.901: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.901: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.902: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.902: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.903: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.903: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.903: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.903: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.903: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.904: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.904: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.904: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.904: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.904: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.905: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.905: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.906: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.906: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.906: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.906: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.906: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.906: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.907: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.907: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.907: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.907: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.908: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.908: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.909: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.909: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.909: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.909: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.909: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.909: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.910: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.910: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.910: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.910: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.911: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.911: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.911: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.912: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.912: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.912: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.912: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.912: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.913: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.913: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.913: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.913: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.914: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.914: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.914: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.914: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.914: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.914: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.915: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.915: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.916: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.916: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.916: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.916: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.917: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.917: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.917: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.917: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.917: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.917: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.918: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.918: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.919: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.919: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.919: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.919: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.919: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.919: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.920: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.920: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.920: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.920: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.921: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.921: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.922: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.922: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.922: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.922: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.922: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.922: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.923: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.923: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.923: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.923: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.924: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.924: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.924: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.924: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.924: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.924: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.925: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.925: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.926: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.926: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.926: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.926: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.927: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.927: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.928: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.928: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.928: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.928: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.928: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.928: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.929: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.929: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.929: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.929: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.930: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.930: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.931: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.931: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.931: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.931: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.932: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.932: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.933: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.933: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.933: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.933: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.934: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.934: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.935: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.935: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.935: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.935: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.935: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.935: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.936: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.936: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.936: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.936: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.936: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.937: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.937: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.937: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.937: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.937: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.938: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.938: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.939: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.939: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.939: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.939: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.939: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.939: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.940: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.940: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.940: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.940: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.941: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.941: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.941: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.941: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.941: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.941: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.942: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.942: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.943: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.943: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.943: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.943: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.943: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.943: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.944: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.944: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.944: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.944: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.945: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.945: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.945: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.945: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.945: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.945: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.946: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.946: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.947: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.947: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.947: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.947: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.947: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.947: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.948: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.948: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.948: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.948: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.949: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.949: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.949: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.949: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.949: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.949: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.950: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.950: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.951: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.951: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.951: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.951: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.951: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.951: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.952: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.952: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.952: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.952: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.953: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.953: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.953: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.954: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.954: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.954: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.954: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.954: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.955: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.955: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.955: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.955: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.955: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.955: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.958: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.958: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.958: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.958: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.959: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.959: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.959: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.959: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.959: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.959: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.960: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.960: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.961: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.961: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.961: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.961: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.961: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.961: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.962: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.962: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.962: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.962: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.963: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.963: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.964: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.964: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.964: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.964: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.964: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.964: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.965: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.965: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.965: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.965: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.966: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.966: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.966: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.966: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.966: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.966: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.966: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.967: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.967: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.968: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.968: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.968: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.968: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.968: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.969: [vfs7552] CAPTURE_NUM_STATES entering state 2 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.969: [vfs7552] REQUEST CHUNK entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.969: Sending vfs7552_read_image_chunk 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.970: [vfs7552] REQUEST CHUNK completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.970: [vfs7552] CAPTURE_NUM_STATES entering state 3 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.970: [vfs7552] CAPTURE_NUM_STATES entering state 4 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.970: Cleaning image 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.970: variance_after = 17 164s 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.971: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.971: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.971: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.971: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.972: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.973: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.973: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.973: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.973: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.973: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.974: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.974: [vfs7552] QUERY DATA READY completed successfully 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.974: [vfs7552] QUERY DATA READY entering state 0 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.974: Sending vfs7552_is_image_ready 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.974: [vfs7552] QUERY DATA READY entering state 1 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.974: Receiving 64 bytes 164s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.975: Got 6 bytes out of 64 164s (process:3126): libfprint-SSM-DEBUG: 05:38:09.975: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.975: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.975: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.976: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.976: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.977: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.977: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.977: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.977: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.978: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.978: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.979: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.979: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.979: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.979: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.980: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.980: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.981: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.981: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.981: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.981: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.981: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.982: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.983: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.983: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.983: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.983: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.984: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.984: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.985: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.985: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.985: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.985: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.986: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.986: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.987: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.987: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.987: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.987: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.988: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.988: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.989: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.989: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.990: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.990: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.990: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.990: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.991: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.991: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.991: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.991: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.992: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.992: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.993: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.993: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.993: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.993: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.994: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.994: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.995: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.995: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.995: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.995: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.996: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.996: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.997: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.997: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.997: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.997: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:09.998: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:09.998: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.000: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.000: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.000: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.000: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.001: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.001: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.002: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.002: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.002: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.002: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.004: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.004: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.005: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.005: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.005: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.005: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.006: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.006: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.007: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.007: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.007: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.007: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.008: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.008: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.009: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.009: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.009: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.009: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.010: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.010: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.012: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.012: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.012: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.012: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.013: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.013: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.013: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.014: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.014: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.014: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.014: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.015: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.016: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.016: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.016: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.016: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.017: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.017: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.018: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.018: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.018: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.018: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.019: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.019: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.020: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.020: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.020: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.020: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.021: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.021: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.022: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.022: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.022: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.022: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.023: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.023: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.024: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.024: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.024: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.024: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.025: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.025: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.026: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.026: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.026: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.026: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.026: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.027: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.028: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.028: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.028: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.028: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.029: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.029: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.030: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.030: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.030: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.030: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.031: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.031: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.032: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.032: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.032: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.032: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.033: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.033: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.034: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.034: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.034: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.034: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.034: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.034: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.035: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.035: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.035: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.035: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.036: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.036: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.037: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.037: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.038: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.038: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.039: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.039: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.040: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.040: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.040: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.040: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.040: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.040: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.041: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.041: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.041: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.041: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.042: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.042: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.043: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.043: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.043: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.043: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.044: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.044: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.045: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.045: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.045: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.045: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.045: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.045: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.046: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.046: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.046: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.046: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.047: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.047: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.048: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.048: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.048: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.048: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.049: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.049: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.049: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.049: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.049: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.049: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.050: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.050: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.051: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.051: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.051: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.051: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.052: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.052: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.052: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.053: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.053: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.053: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.053: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.053: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.055: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.055: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.055: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.055: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.055: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.055: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.056: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.056: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.056: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.056: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.057: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.057: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.058: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.058: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.058: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.058: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.059: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.059: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.060: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.060: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.060: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.060: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.061: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.061: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.062: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.062: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.062: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.062: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.063: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.063: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.064: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.064: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.064: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.064: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.065: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.065: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.066: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.066: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.066: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.066: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.067: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.067: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.068: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.068: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.068: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.068: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.069: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.069: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.069: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.069: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.069: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.069: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.070: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.070: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.071: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.071: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.071: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.071: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.072: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.072: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.073: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.073: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.073: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.073: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.074: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.074: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.075: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.075: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.075: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.075: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.075: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.075: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.076: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.076: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.076: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.076: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.077: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.077: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.078: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.078: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.078: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.078: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.079: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.079: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.080: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.080: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.080: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.080: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.080: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.081: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.081: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.081: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.081: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.081: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.082: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.082: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.083: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.083: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.083: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.083: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.084: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.084: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.085: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.085: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.085: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.085: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.086: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.086: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.087: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.087: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.087: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.087: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.087: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.087: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.088: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.088: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.088: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.088: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.089: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.089: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.090: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.090: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.090: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.090: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.091: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.091: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.092: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.092: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.092: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.092: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.093: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.093: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.094: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.094: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.094: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.094: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.095: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.095: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.095: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.095: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.095: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.095: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.096: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.096: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.097: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.097: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.097: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.097: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.097: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.097: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.098: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.098: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.098: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.098: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.099: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.099: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.100: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.100: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.100: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.100: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.100: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.101: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.101: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.101: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.101: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.101: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.102: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.102: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.103: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.103: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.103: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.103: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.104: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.104: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.104: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.104: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.105: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.105: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.105: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.106: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.106: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.106: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.106: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.106: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.107: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.107: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.108: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.108: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.108: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.108: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.109: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.109: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.109: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.109: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.109: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.109: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.110: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.110: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.111: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.111: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.111: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.111: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.112: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.112: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.113: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.113: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.113: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.113: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.113: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.113: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.114: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.114: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.114: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.114: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.115: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.115: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.116: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.116: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.116: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.116: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.116: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.117: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.117: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.117: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.117: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.117: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.118: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.118: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.119: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.119: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.119: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.119: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.119: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.120: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.120: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.120: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.120: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.120: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.121: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.121: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.122: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.122: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.122: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.122: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.122: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.122: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.123: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.123: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.123: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.123: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.124: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.124: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.125: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.125: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.125: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.125: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.126: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.126: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.127: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.127: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.127: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.127: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.127: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.128: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.128: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.128: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.128: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.128: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.129: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.129: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.130: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.130: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.130: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.130: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.131: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.131: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.132: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.132: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.132: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.132: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.132: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.132: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.133: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.133: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.133: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.133: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.134: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.134: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.135: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.135: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.135: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.135: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.135: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.135: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.136: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.136: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.136: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.136: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.137: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.137: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.138: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.138: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.138: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.138: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.138: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.138: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.139: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.139: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.139: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.139: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.140: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.140: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.141: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.141: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.141: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.141: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.141: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.141: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.142: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.142: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.142: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.142: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.143: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.143: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.143: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.143: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.144: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.144: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.144: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.144: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.145: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.145: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.145: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.145: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.146: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.146: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.147: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.147: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.147: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.147: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.147: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.147: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.148: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.148: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.148: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.148: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.149: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.149: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.150: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.150: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.150: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.150: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.150: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.151: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.151: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.151: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.152: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.152: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.152: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.152: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.153: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.153: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.153: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.153: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.154: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.154: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.154: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.155: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.155: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.155: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.155: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.155: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.156: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.156: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.156: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.156: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.157: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.157: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.158: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.158: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.158: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.158: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.158: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.158: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.159: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.159: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.159: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.159: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.160: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.160: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.161: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.161: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.161: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.161: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.162: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.162: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.162: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.163: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.163: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.163: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.163: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.163: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.164: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.164: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.164: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.164: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.165: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.165: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.166: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.166: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.166: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.166: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.170: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.170: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.171: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.171: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.171: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.171: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.172: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.172: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.173: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.173: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.173: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.173: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.174: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.174: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.174: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.174: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.175: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.175: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.175: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.175: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.176: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.176: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.176: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.176: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.177: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.177: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.178: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.178: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.178: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.178: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.179: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.179: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.179: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.179: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.179: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.179: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.180: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.180: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.181: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.181: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.181: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.181: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.182: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.182: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.183: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.183: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.183: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.183: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.183: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.183: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.184: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.184: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.184: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.184: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.185: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.185: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.186: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.186: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.186: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.186: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.186: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.186: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.187: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.187: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.187: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.187: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.190: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.190: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.191: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.191: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.191: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.191: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.191: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.191: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.192: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.192: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.192: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.192: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.193: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.193: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.194: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.194: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.194: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.194: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.195: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.195: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.195: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.195: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.195: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.195: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.196: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.196: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.197: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.197: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.197: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.197: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.198: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.198: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.198: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.199: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.199: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.199: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.199: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.199: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.200: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.200: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.200: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.200: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.201: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.201: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.201: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.201: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.202: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.202: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.202: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.202: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.203: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.203: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.203: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.203: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.204: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.204: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.204: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.204: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.205: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.205: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.205: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.205: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.206: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.206: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.206: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.206: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.207: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.207: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.208: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.208: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.208: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.208: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.208: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.208: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.209: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.209: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.209: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.209: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.210: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.210: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.211: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.211: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.211: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.211: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.211: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.211: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.212: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.212: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.212: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.212: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.213: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.213: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.214: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.214: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.214: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.214: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.214: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.214: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.215: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.215: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.215: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.215: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.216: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.216: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.216: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.216: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.217: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.217: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.217: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.217: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.218: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.218: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.218: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.218: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.219: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.219: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.219: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.220: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.220: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.220: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.220: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.220: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.221: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.221: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.221: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.221: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.222: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.222: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.222: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.223: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.223: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.223: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.223: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.223: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.224: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.224: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.224: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.224: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.225: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.225: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.226: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.226: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.226: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.226: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.227: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.227: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.228: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.228: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.228: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.228: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.228: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.228: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.229: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.229: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.229: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.229: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.230: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.230: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.231: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.231: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.231: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.232: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.232: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.233: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.233: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.233: variance_after = 20 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.233: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.233: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.234: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.234: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.235: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.235: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.235: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.235: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.236: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.236: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.237: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.237: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.237: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.237: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.238: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.238: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.239: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.239: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.239: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.239: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.239: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.239: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.240: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.240: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.240: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.240: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.241: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.241: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.242: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.242: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.242: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.242: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.243: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.243: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.243: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.243: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.243: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.243: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.244: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.244: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.245: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.245: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.245: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.245: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.246: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.246: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.247: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.247: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.247: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.247: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.248: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.248: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.248: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.249: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.249: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.249: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.249: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.249: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.250: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.250: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.250: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.250: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.251: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.251: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.252: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.252: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.252: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.252: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.253: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.253: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.253: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.253: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.253: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.253: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.254: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.254: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.255: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.255: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.255: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.255: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.256: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.256: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.256: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.257: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.257: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.257: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.257: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.257: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.258: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.258: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.259: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.259: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.259: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.260: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.260: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.260: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.261: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.261: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.261: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.261: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.262: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.262: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.262: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.262: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.263: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.263: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.264: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.264: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.264: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.264: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.265: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.265: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.266: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.266: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.266: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.266: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.267: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.267: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.268: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.268: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.268: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.268: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.269: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.269: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.269: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.269: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.270: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.270: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.270: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.270: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.271: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.271: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.271: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.271: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.272: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.272: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.273: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.273: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.273: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.273: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.273: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.273: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.275: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.275: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.275: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.275: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.276: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.276: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.276: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.277: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.277: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.277: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.277: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.277: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.278: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.278: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.278: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.278: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.279: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.279: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.280: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.280: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.280: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.280: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.281: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.281: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.282: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.282: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.282: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.282: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.282: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.283: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.283: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.283: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.283: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.283: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.284: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.284: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.285: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.285: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.285: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.285: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.286: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.286: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.287: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.287: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.287: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.287: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.288: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.288: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.289: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.289: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.289: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.289: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.290: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.290: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.291: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.291: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.291: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.291: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.292: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.292: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.293: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.293: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.293: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.293: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.294: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.294: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.297: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.297: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.297: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.297: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.298: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.298: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.299: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.299: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.299: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.299: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.300: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.300: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.300: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.300: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.301: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.301: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.301: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.301: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.302: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.302: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.302: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.302: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.303: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.303: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.304: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.304: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.304: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.304: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.305: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.305: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.306: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.306: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.306: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.306: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.307: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.307: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.308: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.308: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.308: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.308: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.309: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.309: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.310: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.310: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.310: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.310: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.311: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.311: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.312: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.312: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.312: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.312: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.313: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.313: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.314: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.314: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.314: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.314: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.315: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.315: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.316: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.316: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.316: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.316: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.317: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.317: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.318: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.318: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.318: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.318: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.319: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.319: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.320: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.320: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.320: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.320: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.320: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.320: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.321: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.321: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.321: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.321: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.322: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.322: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.323: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.323: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.323: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.323: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.324: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.324: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.325: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.325: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.325: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.325: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.326: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.326: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.327: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.327: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.327: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.327: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.328: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.328: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.329: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.329: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.329: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.329: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.331: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.331: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.332: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.332: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.332: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.332: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.333: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.333: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.334: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.334: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.334: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.334: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.335: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.335: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.336: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.336: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.336: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.336: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.337: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.337: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.337: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.337: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.338: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.338: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.338: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.338: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.339: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.339: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.339: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.339: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.340: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.340: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.341: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.341: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.341: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.341: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.342: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.342: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.342: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.342: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.342: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.342: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.343: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.343: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.344: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.344: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.344: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.344: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.345: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.345: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.346: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.346: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.346: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.346: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.347: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.347: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.347: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.347: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.347: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.347: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.348: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.348: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.349: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.349: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.349: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.349: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.350: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.350: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.351: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.351: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.351: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.351: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.352: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.352: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.352: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.352: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.352: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.352: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.353: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.353: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.354: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.354: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.354: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.354: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.355: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.355: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.356: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.356: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.356: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.356: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.356: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.356: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.357: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.357: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.357: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.357: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.358: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.358: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.359: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.359: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.359: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.359: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.360: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.360: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.360: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.360: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.360: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.360: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.361: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.361: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.362: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.362: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.362: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.362: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.363: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.363: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.364: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.364: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.364: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.364: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.365: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.365: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.366: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.366: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.366: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.366: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.367: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.367: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.368: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.368: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.368: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.368: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.369: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.369: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.370: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.370: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.370: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.370: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.370: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.371: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.371: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.372: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.372: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.372: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.372: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.372: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.373: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.373: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.373: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.374: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.374: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.375: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.375: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.376: variance_after = 17 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.376: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.376: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.376: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.377: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.377: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.378: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.378: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.378: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.378: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.379: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.379: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.379: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.379: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.379: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.380: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.380: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.381: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.381: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.381: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.381: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.382: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.382: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.383: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.383: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.383: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.383: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.384: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.384: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.385: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.385: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.385: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.385: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.386: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.386: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.387: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.387: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.387: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.387: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.388: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.388: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.389: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.389: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.389: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.389: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.390: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.390: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.390: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.391: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.391: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.391: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.391: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.391: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.392: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.393: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.393: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.393: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.394: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.394: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.395: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.395: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.395: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.395: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.396: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.396: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.397: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.397: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.397: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.397: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.398: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.398: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.399: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.399: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.399: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.399: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.400: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.400: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.401: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.401: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.401: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.401: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.401: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.402: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.402: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.402: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.402: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.403: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.403: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.403: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.404: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.404: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.405: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.405: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.405: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.405: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.406: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.406: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.406: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.406: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.407: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.407: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.408: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.408: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.408: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.408: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.409: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.409: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.410: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.410: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.410: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.410: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.411: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.411: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.412: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.412: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.412: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.412: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.413: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.413: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.414: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.414: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.414: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.414: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.415: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.415: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.416: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.416: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.416: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.416: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.417: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.417: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.419: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.419: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.419: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.419: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.420: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.420: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.421: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.421: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.421: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.421: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.422: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.422: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.423: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.423: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.423: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.423: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.424: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.424: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.425: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.425: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.425: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.425: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.425: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.425: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.427: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.427: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.427: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.427: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.428: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.428: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.429: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.429: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.429: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.429: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.430: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.430: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.431: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.431: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.431: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.431: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.432: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.432: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.433: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.433: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.433: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.433: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.434: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.434: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.435: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.435: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.435: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.435: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.436: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.436: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.437: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.437: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.437: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.437: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.438: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.438: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.439: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.439: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.439: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.439: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.440: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.440: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.441: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.441: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.441: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.441: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.442: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.442: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.443: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.443: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.443: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.443: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.444: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.444: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.445: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.446: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.446: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.446: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.451: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.451: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.452: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.452: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.452: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.452: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.454: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.454: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.455: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.455: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.455: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.455: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.456: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.456: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.457: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.457: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.457: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.457: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.458: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.458: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.459: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.459: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.460: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.460: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.461: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.461: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.462: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.462: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.462: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.462: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.463: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.463: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.464: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.464: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.465: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.465: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.466: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.466: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.467: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.467: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.467: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.467: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.468: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.468: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.469: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.469: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.469: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.469: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.470: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.470: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.471: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.471: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.471: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.471: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.472: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.472: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.473: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.473: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.473: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.473: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.474: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.474: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.475: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.475: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.475: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.475: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.476: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.476: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.477: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.477: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.477: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.477: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.479: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.479: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.480: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.480: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.480: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.480: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.481: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.481: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.482: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.482: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.482: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.482: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.482: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.483: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.483: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.484: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.484: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.484: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.485: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.485: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.486: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.486: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.486: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.487: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.487: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.488: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.488: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.488: variance_after = 17 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.488: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.488: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.491: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.491: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.492: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.492: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.492: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.492: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.494: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.494: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.495: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.495: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.495: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.495: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.495: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.496: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.497: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.497: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.497: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.497: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.498: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.498: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.499: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.499: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.499: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.499: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.499: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.499: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.501: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.501: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.501: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.501: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.502: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.502: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.502: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.502: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.503: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.503: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.503: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.503: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.504: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.504: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.504: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.504: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.505: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.506: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.507: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.507: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.507: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.507: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.508: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.508: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.510: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.510: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.510: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.510: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.511: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.511: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.512: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.512: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.512: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.512: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.513: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.513: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.514: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.514: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.514: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.514: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.515: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.515: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.516: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.516: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.516: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.516: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.517: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.517: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.519: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.519: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.519: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.519: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.521: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.521: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.522: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.522: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.522: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.522: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.523: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.523: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.524: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.524: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.524: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.524: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.525: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.525: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.526: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.526: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.526: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.526: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.527: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.527: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.528: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.528: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.528: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.528: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.529: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.529: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.530: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.530: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.530: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.530: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.531: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.531: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.532: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.532: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.532: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.532: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.538: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.538: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.539: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.539: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.539: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.539: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.540: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.541: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.541: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.541: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.541: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.541: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.542: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.542: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.544: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.544: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.544: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.544: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.545: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.545: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.546: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.546: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.546: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.546: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.547: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.547: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.548: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.548: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.548: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.548: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.549: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.549: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.552: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.552: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.552: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.552: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.554: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.554: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.555: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.555: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.555: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.555: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.556: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.556: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.557: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.557: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.558: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.558: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.559: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.559: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.560: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.560: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.560: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.560: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.561: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.561: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.562: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.562: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.562: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.563: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.563: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.563: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.564: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.564: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.564: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.564: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.565: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.565: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.566: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.566: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.566: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.566: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.567: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.567: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.568: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.568: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.568: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.568: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.569: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.569: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.570: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.571: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.571: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.571: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.571: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.571: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.572: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.572: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.572: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.572: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.573: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.573: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.574: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.574: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.574: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.574: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.575: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.575: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.576: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.576: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.576: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.576: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.577: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.577: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.577: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.577: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.577: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.577: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.578: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.578: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.579: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.579: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.579: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.579: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.580: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.580: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.581: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.581: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.581: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.581: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.582: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.582: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.582: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.582: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.582: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.582: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.583: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.583: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.586: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.586: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.586: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.586: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.588: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.588: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.590: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.590: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.590: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.590: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.591: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.591: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.592: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.592: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.592: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.592: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.593: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.593: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.594: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.594: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.594: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.594: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.595: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.595: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.595: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.595: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.595: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.595: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.596: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.596: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.597: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.597: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.597: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.597: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.597: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.598: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.598: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.598: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.598: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.598: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.599: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.599: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.600: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.600: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.600: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.601: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.601: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.602: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.602: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.602: variance_after = 17 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.602: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.602: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.603: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.603: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.604: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.604: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.604: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.604: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.605: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.605: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.606: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.606: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.606: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.606: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.606: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.606: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.607: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.607: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.607: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.607: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.608: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.608: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.609: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.609: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.609: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.609: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.610: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.610: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.610: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.610: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.610: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.610: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.611: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.611: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.612: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.612: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.612: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.612: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.613: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.613: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.614: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.614: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.614: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.614: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.614: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.614: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.615: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.615: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.615: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.615: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.616: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.616: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.617: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.617: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.617: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.617: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.618: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.618: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.618: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.618: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.618: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.618: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.619: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.619: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.620: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.620: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.620: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.620: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.621: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.621: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.622: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.622: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.622: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.622: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.623: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.623: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.624: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.624: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.624: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.624: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.625: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.625: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.625: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.625: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.625: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.625: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.626: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.626: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.627: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.627: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.627: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.627: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.628: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.628: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.629: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.629: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.629: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.629: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.629: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.629: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.630: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.630: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.630: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.630: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.631: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.631: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.632: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.632: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.632: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.632: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.633: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.633: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.633: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.633: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.633: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.633: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.634: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.634: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.635: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.635: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.635: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.635: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.636: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.636: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.637: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.637: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.637: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.637: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.637: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.637: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.642: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.642: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.642: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.642: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.643: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.643: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.644: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.644: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.644: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.644: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.645: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.645: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.645: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.645: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.645: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.645: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.646: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.646: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.647: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.647: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.647: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.647: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.648: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.648: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.649: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.649: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.649: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.649: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.649: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.649: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.650: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.650: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.650: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.650: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.651: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.651: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.652: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.652: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.652: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.652: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.653: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.653: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.654: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.654: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.654: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.654: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.655: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.655: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.656: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.656: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.656: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.656: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.657: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.657: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.658: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.658: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.658: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.658: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.658: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.658: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.659: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.659: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.659: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.659: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.660: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.660: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.661: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.661: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.661: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.661: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.662: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.662: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.663: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.663: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.663: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.663: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.663: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.663: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.664: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.664: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.664: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.664: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.665: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.665: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.666: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.666: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.666: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.666: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.667: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.667: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.668: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.668: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.668: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.668: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.669: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.670: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.671: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.671: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.671: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.671: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.672: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.672: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.672: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.672: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.672: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.672: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.674: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.674: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.675: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.675: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.675: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.675: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.676: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.676: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.677: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.677: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.677: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.677: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.677: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.677: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.678: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.678: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.678: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.678: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.679: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.679: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.680: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.680: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.680: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.681: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.681: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.682: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.682: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.682: variance_after = 17 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.682: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.682: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.683: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.683: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.683: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.684: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.684: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.684: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.684: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.684: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.685: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.685: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.685: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.685: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.686: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.686: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.687: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.687: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.687: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.687: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.687: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.687: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.688: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.688: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.688: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.688: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.689: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.689: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.690: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.690: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.690: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.690: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.691: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.691: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.692: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.692: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.692: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.692: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.693: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.693: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.694: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.694: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.694: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.694: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.695: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.695: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.695: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.695: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.695: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.695: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.696: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.696: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.697: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.697: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.697: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.697: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.698: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.698: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.699: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.699: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.699: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.699: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.700: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.700: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.701: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.701: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.701: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.701: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.701: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.701: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.702: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.702: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.702: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.702: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.703: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.703: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.704: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.704: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.704: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.704: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.704: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.705: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.705: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.705: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.705: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.705: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.706: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.706: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.707: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.707: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.707: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.707: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.708: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.708: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.709: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.709: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.709: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.709: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.710: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.710: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.710: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.710: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.710: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.710: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.711: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.711: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.712: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.712: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.712: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.712: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.713: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.713: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.714: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.714: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.714: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.714: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.715: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.715: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.715: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.715: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.715: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.715: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.716: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.716: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.717: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.717: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.717: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.717: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.718: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.718: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.718: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.718: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.718: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.718: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.719: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.719: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.720: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.720: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.720: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.720: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.721: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.721: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.722: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.722: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.722: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.722: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.723: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.723: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.724: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.724: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.724: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.724: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.725: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.725: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.726: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.726: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.726: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.726: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.727: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.727: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.727: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.727: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.727: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.727: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.728: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.728: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.729: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.729: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.729: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.729: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.730: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.730: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.731: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.731: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.731: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.731: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.732: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.732: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.733: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.733: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.733: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.733: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.734: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.734: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.735: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.735: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.735: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.735: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.736: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.736: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.737: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.737: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.737: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.737: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.737: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.737: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.738: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.738: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.738: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.738: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.739: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.739: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.740: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.740: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.740: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.740: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.741: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.741: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.742: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.742: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.742: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.742: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.743: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.743: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.744: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.744: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.744: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.744: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.745: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.745: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.746: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.746: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.746: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.746: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.746: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.746: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.747: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.747: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.747: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.747: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.748: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.748: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.749: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.749: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.749: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.749: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.750: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.750: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.751: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.751: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.751: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.751: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.752: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.752: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.753: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.753: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.753: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.753: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.754: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.754: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.755: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.755: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.755: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.755: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.756: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.756: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.756: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.756: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.756: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.756: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.757: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.757: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.758: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.758: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.758: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.758: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.759: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.759: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.760: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.760: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.760: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.760: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.760: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.761: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.761: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.762: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.762: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.762: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.762: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.762: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.763: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.763: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.763: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.764: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.764: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.765: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.765: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.765: variance_after = 16 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.765: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.765: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.766: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.766: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.767: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.767: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.767: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.767: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.768: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.768: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.768: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.769: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.769: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.769: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.769: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.769: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.770: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.770: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.770: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.770: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.771: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.771: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.772: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.772: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.772: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.772: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.773: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.773: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.774: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.774: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.774: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.774: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.775: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.775: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.775: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.776: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.776: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.776: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.776: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.776: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.777: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.777: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.777: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.777: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.778: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.778: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.779: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.779: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.779: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.779: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.780: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.780: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.781: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.781: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.781: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.781: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.782: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.782: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.783: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.783: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.783: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.783: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.783: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.783: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.784: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.784: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.784: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.784: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.785: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.785: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.786: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.786: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.786: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.786: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.787: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.787: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.788: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.788: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.788: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.788: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.788: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.789: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.789: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.789: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.789: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.789: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.790: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.790: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.792: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.792: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.792: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.792: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.792: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.793: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.793: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.793: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.793: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.793: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.794: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.794: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.795: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.795: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.795: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.795: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.795: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.796: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.796: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.796: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.796: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.796: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.797: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.797: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.798: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.798: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.798: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.798: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.799: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.799: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.800: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.800: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.800: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.800: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.801: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.801: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.802: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.802: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.802: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.802: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.803: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.803: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.804: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.804: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.804: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.804: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.805: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.805: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.806: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.806: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.806: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.806: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.807: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.807: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.807: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.807: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.808: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.808: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.808: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.808: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.809: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.809: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.809: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.809: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.810: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.810: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.811: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.811: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.811: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.811: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.812: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.812: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.813: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.813: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.813: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.813: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.814: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.814: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.814: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.815: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.815: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.815: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.815: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.815: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.816: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.816: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.816: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.816: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.817: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.817: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.818: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.818: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.818: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.818: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.823: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.823: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.824: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.824: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.824: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.824: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.824: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.824: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.825: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.825: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.825: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.825: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.825: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.825: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.826: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.826: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.826: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.826: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.827: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.827: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.828: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.828: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.828: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.828: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.829: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.829: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.829: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.829: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.829: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.829: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.830: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.830: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.831: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.831: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.831: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.831: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.831: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.831: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.832: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.832: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.832: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.832: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.833: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.833: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.833: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.833: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.833: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.833: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.834: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.834: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.835: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.835: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.835: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.835: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.836: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.836: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.836: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.836: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.836: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.836: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.837: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.837: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.838: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.838: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.838: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.838: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.839: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.839: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.840: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.840: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.840: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.840: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.841: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.841: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.841: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.841: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.841: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.841: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.842: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.842: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.843: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.843: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.843: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.843: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.843: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.844: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.844: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.844: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.844: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.844: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.845: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.845: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.846: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.846: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.846: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.846: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.846: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.847: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.847: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.848: variance_after = 17 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.848: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.848: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.848: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.848: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.849: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.849: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.849: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.849: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.850: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.850: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.851: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.851: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.851: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.851: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.852: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.852: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.853: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.853: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.853: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.853: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.854: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.854: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.855: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.855: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.855: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.855: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.855: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.855: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.856: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.856: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.856: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.856: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.857: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.857: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.858: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.858: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.858: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.858: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.859: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.859: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.860: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.860: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.860: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.860: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.861: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.861: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.862: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.862: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.862: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.862: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.862: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.863: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.863: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.863: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.863: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.863: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.864: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.864: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.865: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.865: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.865: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.865: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.865: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.865: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.866: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.866: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.866: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.866: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.867: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.867: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.868: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.868: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.868: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.868: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.869: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.869: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.869: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.869: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.869: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.869: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.870: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.870: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.871: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.871: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.871: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.871: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.872: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.872: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.872: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.872: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.872: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.872: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.873: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.873: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.874: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.875: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.875: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.875: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.876: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.876: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.876: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.876: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.876: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.876: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.877: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.877: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.878: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.878: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.878: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.878: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.879: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.879: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.880: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.880: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.880: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.880: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.880: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.880: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.881: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.881: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.881: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.881: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.882: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.882: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.883: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.883: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.883: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.883: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.883: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.883: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.884: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.884: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.884: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.884: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.885: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.885: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.886: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.886: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.886: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.886: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.886: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.886: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.887: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.887: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.887: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.887: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.888: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.888: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.889: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.889: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.889: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.889: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.890: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.890: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.891: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.891: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.891: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.891: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.891: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.891: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.892: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.892: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.892: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.892: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.893: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.893: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.894: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.894: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.894: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.894: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.895: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.895: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.895: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.895: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.895: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.895: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.896: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.896: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.897: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.897: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.897: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.897: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.898: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.898: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.898: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.898: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.898: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.898: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.899: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.899: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.900: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.900: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.900: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.900: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.900: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.900: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.901: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.901: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.901: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.901: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.902: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.902: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.903: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.903: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.903: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.903: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.904: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.904: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.905: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.905: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.905: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.905: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.905: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.905: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.906: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.906: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.906: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.906: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.907: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.907: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.908: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.908: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.908: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.908: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.908: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.908: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.909: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.909: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.909: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.909: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.910: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.910: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.911: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.911: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.911: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.911: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.911: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.911: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.912: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.912: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.912: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.912: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.913: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.913: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.914: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.914: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.914: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.914: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.914: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.915: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.915: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.916: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.916: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.916: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.916: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.916: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.917: [vfs7552] CAPTURE_NUM_STATES entering state 2 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.917: [vfs7552] REQUEST CHUNK entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.917: Sending vfs7552_read_image_chunk 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.918: [vfs7552] REQUEST CHUNK completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.918: [vfs7552] CAPTURE_NUM_STATES entering state 3 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.919: [vfs7552] CAPTURE_NUM_STATES entering state 4 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.919: Cleaning image 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.919: variance_after = 16 165s 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.919: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.919: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.919: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.919: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.922: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.922: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.922: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.922: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.923: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.923: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.924: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.924: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.924: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.924: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.925: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.925: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.926: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.926: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.926: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.926: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.927: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.927: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.927: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.927: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.927: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.927: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.928: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.928: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.929: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.929: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.929: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.929: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.930: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.930: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.930: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.930: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.930: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.930: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.931: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.931: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.932: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.932: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.932: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.932: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.932: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.932: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.933: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.933: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.933: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.933: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.934: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.934: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.935: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.935: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.935: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.935: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.936: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.936: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.936: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.936: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.936: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.936: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.937: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.937: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.938: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.938: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.938: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.938: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.939: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.939: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.939: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.939: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.939: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.939: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.940: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.940: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.941: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.941: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.941: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.941: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.942: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.942: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.943: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.943: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.943: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.943: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.943: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.943: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.944: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.944: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.944: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.944: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.945: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.945: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.946: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.946: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.946: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.946: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.947: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.947: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.947: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.947: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.947: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.947: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.948: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.948: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.949: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.949: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.949: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.949: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.949: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.950: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.950: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.950: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.950: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.950: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.951: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.951: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.952: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.952: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.952: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.952: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.953: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.953: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.953: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.953: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.953: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.953: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.958: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.958: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.960: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.960: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.960: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.960: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.960: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.960: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.961: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.961: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.961: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.961: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.962: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.962: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.962: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.963: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.963: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.963: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.963: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.963: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.964: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.964: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.964: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.964: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.965: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.965: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.965: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.965: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.965: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.965: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.966: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.966: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.967: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.967: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.967: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.967: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.967: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.967: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.968: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.968: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.968: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.968: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.969: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.969: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.969: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.969: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.969: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.969: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.970: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.970: Receiving 64 bytes 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.971: Got 6 bytes out of 64 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.971: [vfs7552] QUERY DATA READY completed successfully 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.971: [vfs7552] QUERY DATA READY entering state 0 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.971: Sending vfs7552_is_image_ready 165s (process:3126): libfprint-SSM-DEBUG: 05:38:10.971: [vfs7552] QUERY DATA READY entering state 1 165s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.971: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.972: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.972: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.972: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.972: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.973: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.973: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.973: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.973: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.973: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.973: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.974: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.974: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.975: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.975: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.975: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.975: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.975: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.975: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.976: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.976: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.976: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.976: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.977: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.977: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.977: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.977: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.978: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.978: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.978: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.978: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.979: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.979: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.979: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.979: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.980: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.980: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.981: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.981: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.981: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.981: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.982: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.982: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.983: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.983: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.983: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.983: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.983: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.983: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.984: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.984: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.984: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.984: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.985: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.985: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.986: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.986: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.986: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.986: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.986: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.986: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.987: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.987: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.987: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.987: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.987: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.988: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.988: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.988: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.988: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.988: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.989: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.989: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.990: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.990: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.990: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.991: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.991: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.991: [vfs7552] CAPTURE_NUM_STATES entering state 4 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.991: Cleaning image 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:10.991: variance_after = 2168 166s 166s (process:3126): libfprint-SSM-DEBUG: 05:38:10.991: [vfs7552] CAPTURE_NUM_STATES completed successfully 166s (process:3126): libfprint-device-DEBUG: 05:38:10.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 166s (process:3126): libfprint-image_device-DEBUG: 05:38:10.991: Image device reported finger status: on 166s (process:3126): libfprint-image_device-DEBUG: 05:38:10.991: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.041: changing to 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.041: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.041: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.043: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.043: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.043: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.043: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.043: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.043: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.043: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.045: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.045: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.045: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.045: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.045: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.048: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.048: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.049: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.049: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.049: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.050: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.050: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.051: [vfs7552] CAPTURE_NUM_STATES entering state 4 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.051: Cleaning image 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.051: variance_after = 2082 166s 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.051: [vfs7552] CAPTURE_NUM_STATES completed successfully 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.051: Image captured 166s (process:3126): libfprint-image_device-DEBUG: 05:38:11.051: Image device captured an image 166s (process:3126): libfprint-image_device-DEBUG: 05:38:11.052: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 166s (process:3126): libfprint-device-DEBUG: 05:38:11.052: Device reported finger status change: FP_FINGER_STATUS_PRESENT 166s (process:3126): libfprint-image-DEBUG: 05:38:11.079: Minutiae scan completed in 0.027403 secs 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.101: changing to 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.101: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.101: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.102: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.102: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.103: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.103: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.103: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.103: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.103: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.104: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.104: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.104: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.104: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.104: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.105: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.105: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.106: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.106: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.106: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.107: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.107: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.107: [vfs7552] CAPTURE_NUM_STATES entering state 4 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.107: Cleaning image 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.108: variance_after = 2003 166s 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.108: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.108: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.108: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.108: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.109: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.109: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.109: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.109: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.110: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.110: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.111: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.111: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.111: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.111: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.112: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.112: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.112: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.113: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.113: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.113: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.113: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.113: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.114: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.114: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.114: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.114: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.115: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.115: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.115: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.115: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.115: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.115: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.116: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.116: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.117: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.117: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.117: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.117: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.118: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.118: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.118: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.118: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.118: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.118: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.119: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.119: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.120: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.120: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.120: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.120: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.120: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.121: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.121: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.121: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.121: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.121: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.122: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.122: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.123: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.123: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.123: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.123: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.123: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.123: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.124: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.124: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.124: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.124: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.125: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.125: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.125: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.125: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.125: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.125: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.126: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.126: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.127: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.127: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.127: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.127: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.128: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.128: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.128: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.128: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.128: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.128: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.129: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.129: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.130: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.130: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.130: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.130: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.130: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.130: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.131: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.131: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.131: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.131: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.132: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.132: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.132: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.132: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.132: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.132: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.133: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.133: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.134: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.134: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.134: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.134: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.138: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.139: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.139: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.139: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.139: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.139: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.140: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.140: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.141: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.141: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.141: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.141: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.141: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.141: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.142: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.142: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.142: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.142: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.143: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.143: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.144: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.144: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.144: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.144: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.144: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.144: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.145: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.145: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.145: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.145: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.146: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.146: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.147: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.147: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.147: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.147: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.147: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.147: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.148: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.148: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.148: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.148: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.149: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.149: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.150: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.150: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.150: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.150: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.151: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.151: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.152: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.152: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.152: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.152: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.153: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.153: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.154: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.154: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.154: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.154: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.155: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.155: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.155: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.155: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.155: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.155: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.156: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.156: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.157: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.157: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.157: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.157: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.158: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.158: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.158: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.158: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.158: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.158: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.159: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.159: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.160: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.160: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.160: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.160: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.161: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.161: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.162: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.163: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.163: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.163: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.164: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.164: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.165: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.165: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.165: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.165: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.166: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.166: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.167: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.167: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.167: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.167: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.168: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.168: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.169: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.169: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.169: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.169: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.169: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.169: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.170: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.170: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.170: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.170: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.171: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.171: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.172: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.172: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.172: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.172: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.173: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.173: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.173: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.173: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.173: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.173: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.174: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.174: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.175: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.175: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.175: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.175: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.176: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.176: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.177: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.177: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.177: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.177: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.178: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.178: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.179: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.179: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.179: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.179: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.179: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.179: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.180: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.180: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.180: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.180: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.181: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.181: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.181: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.182: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.182: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.182: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.182: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.182: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.183: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.183: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.183: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.183: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.184: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.184: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.184: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.184: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.184: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.184: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.185: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.185: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.186: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.186: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.186: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.186: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.187: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.187: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.188: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.188: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.188: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.188: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.188: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.188: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.189: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.189: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.189: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.189: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.190: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.190: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.191: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.191: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.191: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.191: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.192: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.192: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.193: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.193: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.193: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.193: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.194: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.194: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.196: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.196: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.196: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.196: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.196: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.196: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.198: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.198: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.198: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.198: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.198: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.198: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.199: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.199: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.199: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.199: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.200: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.200: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.201: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.201: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.201: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.201: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.202: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.202: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.203: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.203: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.203: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.203: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.203: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.203: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.204: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.204: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.204: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.204: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.205: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.205: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.206: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.206: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.206: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.206: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.206: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.206: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.207: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.207: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.207: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.207: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.208: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.208: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.208: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.209: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.209: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.209: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.209: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.209: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.210: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.210: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.210: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.210: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.211: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.211: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.212: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.212: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.212: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.212: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.212: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.213: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.213: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.213: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.213: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.213: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.215: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.215: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.216: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.216: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.216: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.216: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.217: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.217: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.218: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.218: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.218: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.218: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.219: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.219: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.220: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.220: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.220: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.220: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.221: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.221: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.222: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.222: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.222: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.222: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.223: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.223: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.223: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.223: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.223: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.223: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.224: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.224: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.225: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.225: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.225: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.225: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.225: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.225: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.226: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.226: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.226: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.226: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.227: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.227: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.228: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.228: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.228: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.228: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.229: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.229: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.230: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.230: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.230: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.230: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.231: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.231: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.232: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.232: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.232: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.232: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.233: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.233: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.234: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.234: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.234: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.234: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.235: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.235: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.236: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.236: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.236: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.236: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.237: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.237: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.238: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.238: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.238: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.238: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.239: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.239: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.240: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.240: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.240: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.240: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.241: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.241: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.242: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.243: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.243: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.243: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.243: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.243: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.244: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.244: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.244: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.244: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.245: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.245: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.246: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.246: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.246: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.246: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.247: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.247: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.248: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.248: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.248: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.248: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.249: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.249: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.251: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.251: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.251: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.251: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.252: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.252: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.253: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.253: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.253: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.253: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.254: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.254: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.255: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.255: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.255: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.255: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.256: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.256: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.257: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.257: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.257: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.257: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.258: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.258: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.259: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.259: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.259: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.259: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.260: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.260: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.261: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.261: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.261: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.261: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.262: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.262: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.263: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.263: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.263: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.263: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.264: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.264: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.265: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.265: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.265: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.265: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.266: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.266: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.267: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.267: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.267: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.267: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.268: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.268: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.269: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.269: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.269: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.269: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.270: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.270: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.271: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.271: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.271: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.271: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.272: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.272: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.273: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.273: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.273: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.273: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.278: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.278: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.279: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.279: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.279: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.279: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.280: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.280: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.281: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.281: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.281: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.281: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.282: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.282: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.283: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.283: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.283: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.283: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.284: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.284: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.285: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.285: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.285: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.285: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.286: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.286: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.287: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.287: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.287: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.287: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.288: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.288: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.289: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.289: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.289: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.289: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.290: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.290: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.291: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.291: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.291: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.291: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.292: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.292: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.293: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.293: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.293: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.293: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.294: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.294: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.295: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.295: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.295: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.295: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.296: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.296: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.297: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.297: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.297: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.297: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.298: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.298: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.299: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.299: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.299: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.299: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.300: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.300: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.301: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.301: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.301: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.301: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.302: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.302: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.303: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.303: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.303: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.303: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.304: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.304: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.304: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.304: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.305: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.305: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.306: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.306: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.307: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.307: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.307: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.307: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.308: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.308: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.309: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.309: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.309: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.309: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.310: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.310: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.311: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.311: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.311: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.311: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.312: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.312: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.313: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.313: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.313: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.313: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.314: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.314: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.315: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.315: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.315: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.315: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.315: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.315: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.317: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.317: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.317: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.317: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.318: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.318: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.319: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.319: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.319: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.319: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.320: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.320: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.322: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.322: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.322: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.322: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.323: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.323: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.324: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.324: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.324: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.324: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.325: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.325: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.326: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.326: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.326: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.326: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.327: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.327: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.328: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.328: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.328: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.328: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.329: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.329: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.329: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.329: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.329: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.329: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.330: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.330: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.331: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.331: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.331: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.331: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.332: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.332: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.333: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.333: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.333: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.333: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.334: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.334: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.335: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.335: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.335: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.335: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.336: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.336: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.337: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.337: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.337: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.337: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.338: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.338: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.339: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.339: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.339: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.339: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.339: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.339: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.340: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.340: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.340: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.340: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.341: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.341: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.343: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.343: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.343: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.343: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.343: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.343: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.344: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.345: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.345: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.345: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.346: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.346: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.346: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.346: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.347: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.347: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.347: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.347: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.348: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.348: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.348: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.348: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.349: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.349: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.350: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.350: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.350: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.350: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.351: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.351: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.352: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.352: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.352: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.352: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.353: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.353: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.354: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.354: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.354: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.354: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.355: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.355: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.355: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.356: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.356: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.356: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.356: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.356: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.357: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.357: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.357: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.357: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.358: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.358: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.359: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.359: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.359: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.359: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.360: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.360: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.361: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.361: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.361: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.361: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.362: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.362: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.362: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.362: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.362: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.362: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.363: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.363: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.364: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.364: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.364: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.364: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.365: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.365: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.365: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.365: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.365: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.365: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.366: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.366: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.367: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.367: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.367: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.367: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.368: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.368: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.369: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.369: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.369: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.369: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.369: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.369: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.370: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.370: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.370: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.370: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.371: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.371: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.372: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.372: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.372: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.372: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.373: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.373: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.374: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.374: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.374: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.374: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.374: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.374: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.375: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.375: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.375: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.375: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.376: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.376: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.377: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.377: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.377: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.377: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.378: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.378: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.379: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.379: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.379: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.379: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.379: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.379: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.380: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.380: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.380: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.380: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.381: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.381: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.382: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.383: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.383: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.383: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.383: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.383: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.384: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.384: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.384: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.384: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.385: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.385: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.386: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.386: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.386: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.386: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.387: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.387: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.388: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.388: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.388: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.388: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.389: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.389: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.390: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.390: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.390: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.390: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.390: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.390: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.391: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.391: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.391: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.391: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.392: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.392: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.393: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.393: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.393: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.393: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.394: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.394: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.395: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.395: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.395: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.395: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.395: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.395: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.396: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.396: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.396: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.396: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.396: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.397: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.397: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.398: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.398: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.398: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.398: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.398: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.399: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.399: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.399: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.400: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.400: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.401: [vfs7552] CAPTURE_NUM_STATES entering state 4 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.401: Cleaning image 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.401: variance_after = 1737 166s 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.401: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.401: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.402: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.402: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.403: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.403: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.403: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.403: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.403: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.403: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.404: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.404: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.404: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.404: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.405: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.405: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.406: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.406: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.406: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.406: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.407: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.407: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.409: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.409: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.409: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.409: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.410: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.410: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.411: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.411: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.411: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.411: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.412: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.412: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.413: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.413: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.413: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.413: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.414: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.414: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.415: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.415: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.415: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.415: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.416: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.416: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.417: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.417: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.417: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.417: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.418: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.418: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.419: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.419: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.419: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.419: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.420: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.420: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.421: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.421: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.421: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.421: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.422: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.422: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.423: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.423: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.423: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.423: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.424: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.424: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.425: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.425: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.425: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.425: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.426: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.426: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.428: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.428: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.428: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.428: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.429: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.429: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.430: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.430: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.430: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.430: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.431: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.431: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.432: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.432: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.432: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.432: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.433: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.433: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.434: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.434: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.434: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.434: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.439: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.439: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.440: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.440: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.440: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.440: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.441: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.441: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.441: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.441: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.441: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.441: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.442: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.442: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.443: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.443: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.443: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.443: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.444: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.444: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.445: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.445: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.445: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.445: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.446: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.446: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.448: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.448: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.448: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.448: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.449: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.449: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.449: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.449: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.450: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.450: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.450: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.450: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.451: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.451: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.451: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.451: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.452: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.452: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.453: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.453: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.453: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.453: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.454: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.454: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.455: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.455: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.455: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.455: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.456: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.456: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.457: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.457: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.457: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.457: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.458: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.458: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.458: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.458: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.458: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.458: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.459: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.459: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.460: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.460: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.460: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.460: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.461: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.461: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.461: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.461: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.461: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.461: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.462: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.462: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.463: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.463: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.463: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.463: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.463: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.464: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.464: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.464: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.464: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.464: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.465: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.465: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.466: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.466: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.466: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.466: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.466: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.466: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.467: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.467: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.467: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.467: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.468: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.468: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.469: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.469: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.469: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.469: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.470: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.470: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.471: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.471: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.471: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.471: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.471: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.471: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.472: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.472: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.472: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.472: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.474: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.474: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.475: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.475: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.475: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.475: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.475: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.475: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.477: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.477: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.477: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.477: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.477: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.477: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.478: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.478: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.478: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.478: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.479: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.479: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.480: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.480: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.480: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.480: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.480: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.480: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.481: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.481: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.481: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.481: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.482: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.482: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.483: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.483: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.483: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.483: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.484: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.484: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.485: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.485: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.485: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.485: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.485: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.485: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.486: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.486: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.486: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.486: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.487: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.487: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.488: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.488: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.488: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.488: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.489: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.489: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.489: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.489: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.489: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.489: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.490: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.490: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.491: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.491: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.491: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.491: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.492: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.492: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.493: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.493: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.493: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.493: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.494: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.494: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.494: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.494: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.494: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.494: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.495: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.495: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.496: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.496: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.496: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.496: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.497: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.497: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.498: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.498: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.498: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.498: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.498: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.498: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.499: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.499: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.499: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.499: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.500: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.500: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.501: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.501: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.501: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.501: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.502: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.502: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.503: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.503: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.503: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.503: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.504: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.504: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.504: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.504: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.504: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.504: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.505: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.505: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.506: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.506: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.506: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.506: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.507: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.507: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.508: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.508: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.508: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.508: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.508: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.508: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.509: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.509: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.509: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.509: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.510: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.510: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.511: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.511: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.511: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.511: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.512: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.512: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.513: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.513: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.513: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.513: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.514: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.514: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.515: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.515: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.515: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.515: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.515: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.515: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.516: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.516: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.516: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.516: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.517: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.517: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.518: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.518: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.518: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.518: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.519: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.519: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.520: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.520: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.520: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.520: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.521: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.521: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.522: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.522: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.522: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.522: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.523: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.523: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.524: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.524: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.524: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.524: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.525: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.525: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.525: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.525: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.525: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.525: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.526: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.526: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.527: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.527: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.527: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.527: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.528: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.528: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.529: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.529: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.529: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.529: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.529: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.529: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.530: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.530: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.530: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.530: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.531: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.531: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.532: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.532: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.532: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.532: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.533: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.533: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.534: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.534: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.534: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.534: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.534: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.534: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.535: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.535: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.535: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.535: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.536: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.536: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.537: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.537: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.537: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.537: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.538: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.538: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.543: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.543: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.543: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.543: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.544: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.544: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.544: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.544: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.544: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.544: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.545: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.545: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.546: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.546: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.546: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.546: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.547: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.547: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.547: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.547: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.548: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.548: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.548: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.548: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.549: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.549: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.549: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.549: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.550: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.550: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.551: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.551: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.551: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.551: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.552: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.552: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.553: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.553: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.553: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.553: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.554: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.554: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.555: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.555: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.555: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.555: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.559: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.559: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.560: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.561: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.561: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.561: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.562: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.562: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.563: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.563: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.563: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.563: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.564: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.564: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.565: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.565: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.565: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.565: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.566: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.566: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.567: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.567: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.567: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.567: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.568: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.568: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.570: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.570: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.570: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.570: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.571: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.571: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.572: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.572: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.572: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.572: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.573: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.573: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.574: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.574: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.574: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.574: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.576: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.576: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.577: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.577: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.577: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.577: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.578: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.578: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.580: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.580: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.580: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.580: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.581: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.581: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.582: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.582: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.582: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.582: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.583: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.583: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.584: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.584: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.584: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.584: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.585: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.585: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.586: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.586: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.586: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.586: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.591: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.591: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.592: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.592: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.592: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.592: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.594: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.594: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.595: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.595: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.595: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.595: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.596: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.596: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.597: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.597: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.597: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.597: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.598: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.598: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.599: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.599: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.599: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.599: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.600: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.600: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.600: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.600: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.600: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.600: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.602: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.602: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.607: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.607: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.607: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.607: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.608: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.608: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.609: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.609: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.609: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.609: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.610: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.610: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.611: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.611: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.611: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.611: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.612: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.612: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.614: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.614: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.614: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.614: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.615: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.615: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.616: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.616: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.616: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.616: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.617: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.617: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.618: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.618: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.618: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.618: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.619: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.619: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.620: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.620: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.620: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.620: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.621: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.621: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.622: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.622: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.622: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.622: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.623: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.623: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.624: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.624: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.624: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.624: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.625: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.626: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.627: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.627: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.627: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.627: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.628: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.628: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.629: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.629: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.629: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.629: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.630: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.630: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.631: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.631: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.632: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.632: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.633: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.633: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.634: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.634: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.634: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.634: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.635: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.635: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.637: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.637: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.637: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.637: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.639: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.639: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.642: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.642: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.642: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.642: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.644: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.644: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.645: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.645: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.646: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.646: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.651: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.651: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.653: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.653: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.653: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.653: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.654: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.654: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.655: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.655: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.655: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.655: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.656: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.656: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.657: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.657: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.657: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.657: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.658: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.658: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.659: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.659: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.659: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.659: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.660: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.660: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.661: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.661: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.662: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.662: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.663: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.663: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.664: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.664: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.664: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.664: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.664: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.665: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.665: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.665: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.665: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.665: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.666: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.666: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.667: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.667: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.667: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.667: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.668: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.668: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.670: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.670: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.670: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.670: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.671: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.671: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.672: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.672: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.672: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.672: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.673: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.673: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.674: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.674: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.674: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.674: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.675: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.675: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.676: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.676: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.676: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.676: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.677: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.677: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.678: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.678: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.678: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.678: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.679: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.679: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.680: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.680: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.680: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.680: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.681: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.681: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.682: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.682: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.683: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.683: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.684: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.684: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.685: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.685: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.685: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.685: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.686: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.686: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.687: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.687: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.687: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.687: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.688: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.688: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.689: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.689: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.689: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.689: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.695: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.695: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.696: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.696: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.696: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.696: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.697: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.697: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.698: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.698: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.699: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.699: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.700: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.700: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.701: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.701: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.701: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.701: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.702: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.702: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.705: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.706: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.706: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.706: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.709: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.710: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.711: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.711: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.711: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.711: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.713: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.713: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.714: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.714: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.714: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.714: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.715: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.715: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.716: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.716: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.716: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.716: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.717: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.717: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.718: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.718: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.718: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.718: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.719: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.719: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.720: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.720: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.720: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.720: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.720: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.721: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.721: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.722: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.722: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.722: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.723: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.723: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.724: [vfs7552] CAPTURE_NUM_STATES entering state 2 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.724: [vfs7552] REQUEST CHUNK entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.724: Sending vfs7552_read_image_chunk 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.725: [vfs7552] REQUEST CHUNK completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.725: [vfs7552] CAPTURE_NUM_STATES entering state 3 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.726: [vfs7552] CAPTURE_NUM_STATES entering state 4 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.726: Cleaning image 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.726: variance_after = 1526 166s 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.727: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.727: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.727: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.727: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.728: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.728: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.729: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.729: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.730: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.730: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.731: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.731: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.731: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.731: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.732: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.732: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.733: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.733: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.733: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.733: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.734: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.734: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.736: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.736: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.736: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.736: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.737: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.737: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.738: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.738: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.738: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.739: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.739: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.739: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.740: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.740: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.741: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.741: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.742: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.742: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.743: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.743: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.743: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.743: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.744: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.744: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.745: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.745: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.745: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.745: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.746: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.746: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.747: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.747: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.747: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.747: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.748: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.748: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.749: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.749: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.749: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.749: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.750: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.750: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.751: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.751: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.751: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.751: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.753: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.753: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.753: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.754: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.754: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.754: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.755: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.755: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.756: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.756: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.756: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.756: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.757: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.757: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.758: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.758: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.758: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.758: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.759: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.759: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.760: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.760: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.760: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.760: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.761: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.761: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.762: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.762: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.762: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.762: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.764: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.764: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.765: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.765: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.765: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.765: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.766: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.766: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.767: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.767: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.767: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.767: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.768: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.768: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.769: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.769: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.769: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.769: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.770: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.770: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.772: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.772: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.772: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.772: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.773: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.773: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.774: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.774: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.774: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.774: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.776: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.776: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.778: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.778: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.778: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.778: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.779: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.779: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.780: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.780: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.780: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.780: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.781: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.781: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.783: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.783: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.783: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.783: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.784: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.784: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.784: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.785: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.785: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.785: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.786: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.786: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.787: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.787: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.787: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.787: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.788: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.788: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.789: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.789: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.789: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.789: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.790: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.790: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.791: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.791: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.791: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.791: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.792: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.792: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.793: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.793: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.793: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.793: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.794: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.794: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.795: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.795: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.795: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.795: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.796: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.796: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.797: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.797: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.797: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.797: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.798: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.798: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.799: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.799: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.799: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.799: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.801: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.801: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.802: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.802: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.802: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.802: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.803: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.803: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.805: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.805: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.805: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.805: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.806: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.806: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.807: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.807: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.808: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.808: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.809: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.809: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.810: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.810: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.810: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.810: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.811: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.811: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.812: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.812: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.813: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.813: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.814: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.814: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.815: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.815: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.815: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.815: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.816: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.816: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.817: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.817: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.817: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.817: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.818: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.818: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.819: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.819: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.819: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.819: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.821: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.821: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.822: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.822: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.822: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.822: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.823: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.823: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.825: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.825: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.825: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.825: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.826: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.826: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.827: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.827: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.827: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.827: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.828: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.828: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.829: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.829: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.829: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.829: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.831: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.831: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.832: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.832: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.832: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.832: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.833: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.833: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.834: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.834: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.834: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.835: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.836: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.836: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.837: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.837: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.837: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.837: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.838: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.838: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.840: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.840: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.840: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.840: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.841: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.841: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.842: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.842: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.842: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.842: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.843: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.843: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.845: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.845: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.845: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.845: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.846: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.846: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.847: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.847: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.847: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.847: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.848: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.848: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.849: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.849: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.849: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.849: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.850: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.850: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.851: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.851: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.851: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.851: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.852: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.852: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.853: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.853: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.853: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.853: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.855: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.855: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.856: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.856: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.856: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.856: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.857: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.857: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.858: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.858: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.858: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.858: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.859: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.859: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.861: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.861: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.861: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.861: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.862: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.862: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.863: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.863: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.863: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.863: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.864: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.864: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.865: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.865: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.865: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.865: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.866: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.866: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.867: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.867: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.867: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.867: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.868: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.868: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.869: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.870: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.870: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.870: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.871: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.871: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.872: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.872: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.872: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.872: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.873: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.873: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.874: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.874: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.874: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.874: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.875: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.875: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.876: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.876: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.876: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.876: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.877: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.877: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.878: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.878: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.878: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.878: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.879: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.879: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.880: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.880: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.880: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.881: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.882: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.882: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.882: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.882: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.883: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.883: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.883: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.883: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.884: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.885: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.885: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.885: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.885: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.885: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.887: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.887: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.887: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.887: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.888: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.888: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.889: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.889: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.889: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.889: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.890: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.890: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.891: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.891: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.891: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.891: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.892: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.892: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.893: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.893: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.893: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.893: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.894: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.894: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.895: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.895: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.895: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.895: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.897: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.897: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.898: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.898: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.898: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.898: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.899: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.899: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.900: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.901: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.901: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.901: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.902: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.902: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.903: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.903: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.903: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.903: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.904: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.904: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.905: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.905: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.905: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.905: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.906: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.906: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.907: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.907: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.907: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.907: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.909: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.909: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.910: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.910: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.910: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.910: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.911: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.911: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.912: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.912: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.912: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.912: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.913: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.913: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.914: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.914: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.914: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.914: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.915: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.915: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.917: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.917: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.917: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.917: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.918: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.918: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.919: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.919: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.919: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.919: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.920: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.920: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.921: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.921: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.921: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.921: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.922: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.922: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.924: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.924: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.924: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.924: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.925: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.925: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.927: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.927: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.927: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.927: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.927: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.927: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.929: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.929: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.929: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.929: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.930: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.930: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.931: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.931: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.931: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.931: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.932: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.932: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.933: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.933: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.933: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.933: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.934: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.934: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.935: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.935: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.935: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.935: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.936: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.936: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.937: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.937: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.937: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.937: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.939: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.939: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.940: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.940: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.940: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.940: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.941: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.941: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.942: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.942: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.942: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.942: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.944: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.944: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.945: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.945: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.945: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.945: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.946: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.946: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.947: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.947: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.947: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.947: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.948: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.948: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.949: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.949: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.949: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.949: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.950: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.950: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.951: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.951: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.951: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.951: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.952: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.952: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.953: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.953: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.953: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.954: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.954: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.954: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.956: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.956: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.956: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.956: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.957: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.957: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.958: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.958: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.958: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.958: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.960: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.960: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.961: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.961: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.961: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.961: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.962: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.962: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.963: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.963: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.963: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.963: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.964: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.964: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.965: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.965: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.965: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.965: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.967: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.967: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.968: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.968: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.968: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.968: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.969: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.969: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.971: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.971: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.971: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.971: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.972: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.972: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.973: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.973: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.973: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.973: Sending vfs7552_is_image_ready 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.974: [vfs7552] QUERY DATA READY entering state 1 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.974: Receiving 64 bytes 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.975: Got 6 bytes out of 64 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.975: [vfs7552] QUERY DATA READY completed successfully 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 166s (process:3126): libfprint-SSM-DEBUG: 05:38:11.975: [vfs7552] QUERY DATA READY entering state 0 166s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.975: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.976: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.976: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.977: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.977: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.977: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.977: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.978: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.978: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.979: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.979: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.979: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.979: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.980: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.980: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.981: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.981: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.981: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.981: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.982: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.982: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.984: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.984: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.984: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.984: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.985: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.985: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.986: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.986: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.986: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.986: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.987: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.987: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.988: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.988: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.988: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.988: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.989: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.989: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.990: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.990: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.990: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.990: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.992: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.992: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.993: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.993: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.993: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.993: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.994: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.994: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.995: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.995: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.995: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.995: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.996: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.996: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.997: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.997: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.997: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.997: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:11.999: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:11.999: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.000: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.000: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.000: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.000: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.001: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.001: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.002: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.002: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.002: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.003: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.004: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.004: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.005: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.005: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.005: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.005: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.006: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.006: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.007: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.007: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.007: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.007: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.008: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.008: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.009: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.009: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.009: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.009: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.010: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.010: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.011: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.012: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.012: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.012: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.013: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.013: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.014: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.014: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.014: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.014: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.015: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.015: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.017: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.017: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.017: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.017: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.018: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.018: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.019: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.019: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.019: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.019: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.021: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.021: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.022: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.022: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.022: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.022: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.023: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.023: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.024: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.024: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.024: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.024: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.025: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.025: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.026: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.026: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.026: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.026: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.028: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.028: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.029: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.029: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.029: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.029: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.030: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.030: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.031: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.031: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.031: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.031: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.032: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.032: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.033: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.033: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.033: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.033: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.034: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.034: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.036: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.036: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.036: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.036: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.037: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.037: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.038: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.038: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.038: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.038: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.040: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.040: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.041: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.041: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.041: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.041: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.042: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.042: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.043: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.043: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.043: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.043: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.044: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.044: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.045: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.045: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.045: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.045: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.046: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.046: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.047: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.047: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.047: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.047: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.049: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.049: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.050: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.050: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.050: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.050: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.051: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.051: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.052: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.052: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.052: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.052: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.053: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.053: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.055: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.055: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.055: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.055: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.056: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.056: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.057: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.057: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.057: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.057: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.058: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.058: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.059: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.059: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.059: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.059: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.060: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.060: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.061: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.061: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.061: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.061: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.062: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.062: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.063: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.063: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.063: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.063: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.064: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.064: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.066: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.066: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.066: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.066: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.067: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.067: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.068: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.068: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.068: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.068: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.068: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.069: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.069: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.070: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.070: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.070: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.071: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.071: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.072: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.072: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.072: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.073: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.073: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.074: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.074: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.074: variance_after = 1435 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.074: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.074: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.075: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.075: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.076: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.076: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.076: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.076: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.077: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.077: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.078: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.078: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.078: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.078: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.079: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.079: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.081: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.081: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.081: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.081: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.081: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.081: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.082: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.082: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.082: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.082: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.083: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.083: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.084: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.084: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.085: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.085: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.085: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.085: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.087: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.087: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.087: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.087: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.088: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.088: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.089: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.089: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.089: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.089: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.090: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.090: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.091: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.091: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.091: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.091: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.092: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.092: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.093: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.093: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.093: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.093: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.095: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.095: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.096: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.096: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.096: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.096: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.097: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.097: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.098: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.098: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.098: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.098: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.100: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.100: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.101: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.101: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.101: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.101: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.102: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.102: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.104: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.104: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.104: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.104: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.105: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.105: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.106: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.106: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.106: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.106: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.107: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.107: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.108: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.108: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.108: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.108: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.109: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.109: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.110: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.110: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.110: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.110: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.111: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.111: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.112: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.112: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.112: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.112: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.113: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.113: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.115: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.115: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.115: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.115: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.115: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.115: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.117: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.117: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.117: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.117: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.117: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.117: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.118: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.118: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.118: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.118: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.119: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.119: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.120: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.120: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.120: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.120: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.121: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.121: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.122: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.122: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.122: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.122: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.123: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.123: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.124: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.124: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.124: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.124: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.125: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.125: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.126: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.126: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.126: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.126: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.128: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.128: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.129: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.129: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.129: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.129: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.130: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.130: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.131: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.131: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.131: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.131: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.132: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.132: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.133: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.133: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.133: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.133: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.134: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.134: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.135: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.135: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.135: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.135: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.136: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.136: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.137: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.137: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.137: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.137: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.138: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.138: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.139: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.139: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.139: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.139: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.140: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.140: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.141: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.141: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.141: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.141: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.142: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.142: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.143: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.143: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.143: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.143: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.144: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.144: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.145: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.145: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.145: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.145: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.146: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.146: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.147: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.147: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.147: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.147: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.148: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.148: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.149: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.149: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.149: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.149: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.150: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.150: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.151: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.151: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.151: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.151: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.152: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.152: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.153: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.153: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.153: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.153: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.154: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.154: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.155: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.155: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.155: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.155: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.156: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.156: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.158: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.158: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.158: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.158: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.159: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.159: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.160: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.160: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.160: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.160: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.161: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.161: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.162: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.162: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.162: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.162: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.163: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.163: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.164: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.164: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.164: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.164: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.166: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.166: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.167: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.167: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.167: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.167: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.169: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.169: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.170: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.170: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.170: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.170: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.171: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.171: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.172: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.172: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.172: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.172: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.173: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.173: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.174: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.174: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.174: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.174: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.175: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.175: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.176: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.176: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.176: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.176: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.177: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.177: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.178: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.178: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.178: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.178: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.179: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.179: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.180: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.180: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.180: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.180: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.181: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.181: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.182: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.182: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.182: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.182: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.183: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.183: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.184: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.184: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.184: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.184: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.185: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.185: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.186: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.186: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.186: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.186: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.187: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.187: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.188: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.188: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.188: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.188: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.189: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.189: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.190: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.190: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.190: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.190: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.191: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.191: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.192: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.192: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.192: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.192: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.193: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.193: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.195: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.195: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.195: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.195: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.196: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.196: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.197: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.197: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.197: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.197: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.198: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.198: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.199: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.199: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.199: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.199: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.200: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.200: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.201: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.201: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.201: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.201: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.202: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.202: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.203: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.203: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.204: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.204: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.204: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.204: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.205: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.205: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.205: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.205: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.206: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.206: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.207: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.207: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.207: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.207: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.208: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.208: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.209: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.209: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.209: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.209: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.211: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.211: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.212: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.212: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.212: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.212: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.213: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.213: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.214: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.214: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.214: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.214: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.215: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.215: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.216: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.216: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.216: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.216: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.217: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.217: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.218: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.218: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.218: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.218: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.219: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.219: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.219: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.220: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.220: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.220: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.220: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.220: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.221: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.221: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.221: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.221: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.222: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.222: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.224: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.224: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.224: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.224: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.225: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.225: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.226: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.226: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.226: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.226: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.227: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.227: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.228: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.228: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.229: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.229: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.230: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.230: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.231: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.231: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.231: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.231: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.232: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.232: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.233: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.233: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.233: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.233: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.235: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.235: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.236: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.236: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.236: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.236: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.237: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.237: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.238: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.238: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.238: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.238: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.239: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.239: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.240: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.240: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.240: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.240: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.241: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.241: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.242: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.242: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.242: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.242: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.243: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.243: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.244: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.244: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.244: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.244: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.245: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.245: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.246: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.246: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.246: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.246: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.247: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.247: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.248: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.248: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.248: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.248: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.249: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.249: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.250: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.250: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.250: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.250: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.251: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.251: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.252: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.252: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.252: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.252: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.253: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.253: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.254: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.254: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.254: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.254: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.255: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.255: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.256: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.256: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.257: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.257: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.257: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.257: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.259: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.259: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.259: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.259: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.260: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.260: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.261: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.261: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.261: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.261: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.262: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.262: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.263: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.263: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.263: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.263: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.264: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.264: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.266: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.266: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.266: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.266: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.266: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.266: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.267: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.267: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.268: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.268: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.268: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.268: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.269: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.269: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.269: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.269: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.270: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.270: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.271: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.271: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.271: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.271: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.272: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.272: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.273: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.273: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.273: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.273: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.274: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.274: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.275: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.275: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.275: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.275: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.276: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.276: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.277: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.277: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.277: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.277: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.283: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.283: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.284: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.284: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.284: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.284: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.285: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.285: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.287: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.287: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.287: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.287: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.288: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.288: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.289: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.289: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.289: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.289: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.291: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.291: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.292: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.292: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.292: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.292: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.293: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.293: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.294: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.294: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.294: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.294: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.296: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.296: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.297: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.297: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.297: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.297: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.298: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.298: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.300: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.300: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.300: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.300: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.301: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.301: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.302: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.302: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.302: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.302: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.302: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.302: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.303: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.303: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.303: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.303: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.304: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.304: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.305: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.305: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.305: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.305: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.307: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.307: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.308: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.308: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.308: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.308: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.309: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.309: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.310: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.310: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.310: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.310: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.311: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.311: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.311: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.311: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.312: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.312: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.312: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.312: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.313: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.313: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.313: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.313: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.314: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.314: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.315: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.315: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.315: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.315: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.316: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.316: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.318: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.318: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.318: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.318: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.318: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.318: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.319: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.319: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.319: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.319: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.320: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.320: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.321: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.321: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.321: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.321: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.322: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.322: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.323: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.323: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.323: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.323: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.324: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.324: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.325: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.325: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.325: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.325: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.326: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.326: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.327: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.327: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.327: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.327: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.328: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.328: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.329: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.329: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.329: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.329: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.329: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.329: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.331: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.331: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.331: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.331: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.332: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.332: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.333: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.333: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.333: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.333: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.333: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.333: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.334: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.334: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.334: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.334: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.335: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.335: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.336: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.336: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.336: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.336: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.337: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.337: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.338: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.338: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.338: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.338: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.339: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.339: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.340: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.340: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.340: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.340: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.341: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.341: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.341: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.341: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.342: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.342: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.342: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.342: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.343: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.343: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.343: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.343: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.344: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.344: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.345: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.345: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.345: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.345: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.346: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.346: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.347: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.347: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.347: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.347: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.348: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.348: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.349: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.349: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.349: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.349: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.350: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.350: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.351: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.351: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.351: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.351: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.352: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.352: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.353: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.353: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.353: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.353: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.354: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.354: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.355: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.355: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.355: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.355: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.356: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.356: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.357: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.357: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.357: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.357: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.358: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.358: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.359: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.359: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.359: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.359: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.360: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.360: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.361: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.361: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.361: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.361: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.361: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.361: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.362: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.362: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.362: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.362: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.363: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.363: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.364: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.364: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.364: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.364: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.365: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.365: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.366: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.366: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.366: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.366: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.367: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.367: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.368: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.368: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.368: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.368: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.369: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.369: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.369: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.369: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.369: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.369: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.370: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.370: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.371: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.371: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.371: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.371: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.372: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.372: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.373: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.373: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.373: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.373: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.374: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.374: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.375: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.375: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.375: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.375: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.376: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.376: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.377: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.377: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.377: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.377: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.378: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.378: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.378: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.378: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.378: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.378: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.378: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.379: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.379: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.380: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.380: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.380: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.381: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.381: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.382: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.382: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.382: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.383: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.383: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.384: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.384: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.384: variance_after = 1425 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.384: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.384: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.385: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.385: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.386: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.386: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.386: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.386: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.387: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.387: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.388: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.388: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.388: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.388: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.389: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.389: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.390: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.390: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.390: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.390: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.391: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.391: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.392: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.392: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.392: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.392: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.393: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.393: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.394: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.394: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.394: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.394: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.395: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.395: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.396: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.396: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.396: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.396: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.397: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.397: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.398: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.398: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.398: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.398: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.403: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.403: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.404: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.404: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.404: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.404: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.405: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.405: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.406: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.406: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.406: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.406: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.406: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.406: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.407: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.407: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.407: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.407: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.408: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.408: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.409: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.409: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.409: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.409: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.410: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.410: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.414: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.414: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.414: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.414: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.415: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.415: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.416: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.416: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.416: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.416: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.417: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.417: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.418: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.418: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.418: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.418: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.419: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.419: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.420: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.420: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.420: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.420: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.421: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.421: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.422: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.422: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.422: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.422: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.423: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.423: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.423: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.423: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.423: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.423: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.424: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.424: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.425: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.425: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.425: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.425: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.426: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.426: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.427: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.427: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.427: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.427: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.431: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.431: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.432: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.432: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.432: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.432: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.433: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.433: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.434: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.434: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.434: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.434: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.434: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.434: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.435: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.435: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.435: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.435: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.439: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.439: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.439: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.439: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.439: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.439: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.440: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.440: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.441: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.441: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.441: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.441: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.442: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.442: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.442: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.442: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.442: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.442: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.443: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.443: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.444: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.444: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.444: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.444: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.444: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.444: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.445: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.445: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.445: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.445: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.446: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.446: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.447: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.447: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.447: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.447: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.447: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.447: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.448: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.448: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.448: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.448: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.449: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.449: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.449: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.449: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.449: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.449: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.450: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.450: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.451: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.451: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.451: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.451: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.451: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.451: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.452: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.452: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.452: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.452: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.453: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.453: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.454: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.454: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.454: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.454: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.455: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.455: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.456: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.456: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.456: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.456: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.456: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.456: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.457: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.457: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.457: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.457: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.458: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.458: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.459: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.459: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.459: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.459: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.459: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.459: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.460: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.460: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.460: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.460: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.461: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.461: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.462: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.462: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.462: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.462: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.462: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.462: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.463: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.463: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.463: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.463: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.464: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.464: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.464: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.464: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.464: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.464: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.465: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.465: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.466: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.466: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.466: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.466: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.466: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.466: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.467: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.467: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.467: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.467: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.468: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.468: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.468: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.468: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.468: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.468: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.469: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.469: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.470: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.470: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.470: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.470: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.471: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.471: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.472: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.472: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.472: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.472: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.472: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.472: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.473: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.473: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.473: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.473: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.474: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.474: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.475: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.475: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.475: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.475: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.475: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.475: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.476: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.476: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.476: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.476: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.477: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.477: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.477: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.478: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.478: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.478: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.478: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.478: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.479: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.479: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.479: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.479: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.480: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.480: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.480: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.480: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.480: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.480: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.481: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.481: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.482: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.482: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.482: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.482: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.487: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.487: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.488: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.488: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.488: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.488: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.489: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.489: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.490: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.490: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.490: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.490: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.491: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.491: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.491: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.491: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.491: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.491: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.492: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.492: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.493: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.493: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.493: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.493: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.493: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.494: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.494: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.494: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.494: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.494: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.495: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.495: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.496: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.496: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.496: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.496: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.496: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.496: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.497: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.497: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.497: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.497: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.498: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.498: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.499: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.499: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.499: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.499: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.499: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.499: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.500: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.500: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.500: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.500: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.501: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.501: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.501: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.501: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.502: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.502: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.502: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.502: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.503: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.503: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.503: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.503: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.503: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.504: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.504: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.504: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.504: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.504: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.505: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.505: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.506: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.506: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.506: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.506: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.506: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.506: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.506: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.507: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.507: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.507: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.508: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.508: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.509: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.509: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.509: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.511: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.511: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.512: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.512: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.512: variance_after = 1532 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.512: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.512: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.513: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.513: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.514: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.514: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.514: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.514: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.515: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.515: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.515: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.515: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.515: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.515: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.516: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.516: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.517: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.517: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.517: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.517: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.518: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.518: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.519: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.519: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.519: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.519: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.519: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.519: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.520: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.520: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.520: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.520: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.521: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.521: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.522: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.522: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.522: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.522: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.523: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.523: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.523: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.523: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.523: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.523: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.524: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.524: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.525: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.525: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.525: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.525: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.525: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.526: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.526: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.526: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.526: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.526: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.527: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.527: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.528: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.528: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.528: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.528: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.529: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.529: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.530: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.530: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.530: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.530: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.531: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.531: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.531: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.531: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.532: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.532: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.532: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.532: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.533: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.533: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.533: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.533: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.534: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.534: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.535: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.535: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.535: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.535: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.535: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.535: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.536: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.536: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.536: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.536: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.537: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.537: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.537: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.537: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.537: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.537: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.538: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.538: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.539: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.539: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.539: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.539: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.540: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.540: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.540: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.540: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.540: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.540: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.541: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.541: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.542: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.542: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.542: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.542: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.542: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.542: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.543: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.543: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.543: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.543: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.544: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.544: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.545: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.545: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.545: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.545: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.546: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.546: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.547: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.547: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.547: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.547: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.547: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.547: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.548: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.548: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.548: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.548: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.549: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.549: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.550: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.550: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.550: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.550: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.550: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.550: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.551: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.551: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.551: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.551: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.552: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.552: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.552: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.552: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.552: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.552: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.553: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.553: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.554: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.554: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.554: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.554: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.555: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.555: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.555: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.555: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.555: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.555: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.556: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.556: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.557: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.557: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.557: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.557: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.558: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.558: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.559: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.559: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.559: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.559: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.560: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.560: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.560: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.561: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.561: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.561: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.561: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.562: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.563: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.563: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.563: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.563: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.563: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.564: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.564: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.564: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.564: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.564: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.565: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.565: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.566: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.566: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.566: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.566: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.567: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.567: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.568: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.568: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.568: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.568: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.569: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.569: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.570: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.570: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.570: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.570: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.571: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.571: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.572: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.572: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.572: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.572: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.572: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.572: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.573: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.573: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.573: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.573: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.573: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.574: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.574: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.575: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.575: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.575: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.576: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.576: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.577: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.577: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.577: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.578: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.578: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.578: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.578: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.578: variance_after = 1691 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.578: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.578: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.579: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.579: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.580: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.580: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.580: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.580: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.581: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.581: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.582: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.582: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.582: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.582: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.583: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.583: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.584: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.584: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.584: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.584: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.585: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.585: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.585: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.586: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.586: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.586: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.586: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.586: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.587: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.587: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.587: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.587: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.588: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.588: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.589: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.589: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.589: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.589: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.590: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.590: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.590: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.590: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.590: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.590: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.591: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.591: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.592: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.592: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.592: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.592: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.593: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.593: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.593: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.593: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.593: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.593: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.594: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.594: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.595: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.595: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.595: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.595: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.596: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.596: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.597: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.597: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.597: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.597: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.598: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.598: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.599: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.599: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.599: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.599: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.600: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.600: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.601: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.601: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.601: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.601: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.601: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.601: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.602: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.602: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.602: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.602: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.603: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.603: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.604: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.604: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.604: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.604: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.605: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.605: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.606: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.606: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.606: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.606: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.607: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.607: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.608: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.608: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.608: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.608: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.608: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.609: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.609: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.609: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.609: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.609: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.610: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.610: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.611: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.611: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.611: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.611: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.612: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.612: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.619: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.619: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.619: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.619: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.620: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.620: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.621: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.621: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.621: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.621: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.621: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.621: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.622: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.622: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.622: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.622: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.623: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.623: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.624: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.624: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.624: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.624: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.625: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.625: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.625: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.625: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.625: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.625: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.626: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.626: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.627: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.627: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.627: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.627: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.628: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.628: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.629: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.629: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.629: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.629: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.630: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.630: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.631: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.631: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.631: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.631: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.632: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.632: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.633: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.633: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.633: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.633: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.634: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.634: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.634: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.634: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.634: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.634: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.635: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.635: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.636: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.636: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.636: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.636: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.639: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.639: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.640: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.640: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.640: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.640: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.640: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.640: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.641: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.641: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.641: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.641: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.642: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.642: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.643: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.643: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.643: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.643: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.644: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.644: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.644: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.645: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.645: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.645: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.645: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.645: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.646: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.646: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.646: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.646: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.647: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.647: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.647: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.647: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.647: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.647: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.648: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.648: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.649: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.649: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.649: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.649: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.649: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.649: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.650: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.650: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.650: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.650: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.651: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.651: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.652: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.652: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.652: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.652: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.652: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.652: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.653: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.653: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.653: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.653: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.653: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.654: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.654: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.655: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.655: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.655: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.656: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.656: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.656: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.656: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.656: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.657: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.657: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.658: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.658: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.658: variance_after = 1845 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.658: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.658: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.659: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.659: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.659: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.659: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.659: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.659: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.660: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.660: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.661: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.661: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.661: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.661: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.661: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.661: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.662: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.662: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.662: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.662: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.663: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.663: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.663: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.663: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.663: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.663: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.664: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.664: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.665: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.665: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.665: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.665: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.665: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.665: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.666: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.666: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.666: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.666: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.667: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.667: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.668: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.668: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.668: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.668: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.668: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.668: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.669: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.669: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.669: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.669: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.670: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.670: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.675: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.675: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.675: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.675: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.676: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.676: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.679: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.679: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.679: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.679: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.679: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.679: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.680: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.680: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.680: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.680: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.681: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.681: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.682: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.682: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.682: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.682: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.682: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.682: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.683: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.683: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.683: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.683: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.684: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.684: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.685: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.685: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.685: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.685: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.687: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.687: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.687: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.688: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.688: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.688: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.688: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.688: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.689: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.689: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.689: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.689: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.690: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.690: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.691: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.691: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.691: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.691: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.692: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.692: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.692: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.693: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.693: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.693: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.694: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.694: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.695: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.695: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.695: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.695: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.696: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.696: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.696: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.696: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.697: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.697: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.697: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.697: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.698: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.698: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.698: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.698: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.699: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.699: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.700: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.700: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.700: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.700: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.701: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.701: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.702: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.702: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.702: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.702: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.703: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.703: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.704: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.704: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.704: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.704: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.705: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.705: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.705: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.706: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.706: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.706: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.706: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.706: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.707: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.707: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.707: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.707: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.708: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.708: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.709: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.709: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.709: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.709: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.710: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.710: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.711: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.711: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.711: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.711: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.712: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.712: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.713: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.713: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.713: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.713: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.714: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.714: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.715: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.715: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.715: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.715: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.716: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.716: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.717: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.717: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.717: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.717: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.718: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.718: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.718: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.718: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.718: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.718: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.719: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.719: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.720: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.720: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.720: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.720: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.720: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.721: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.721: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.721: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.721: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.721: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.722: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.722: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.723: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.723: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.723: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.723: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.723: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.723: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.724: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.724: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.724: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.724: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.725: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.725: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.725: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.725: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.725: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.725: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.726: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.726: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.727: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.727: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.727: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.727: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.727: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.727: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.728: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.728: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.728: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.728: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.729: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.729: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.729: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.729: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.729: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.730: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.730: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.730: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.731: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.731: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.731: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.731: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.732: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.732: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.735: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.735: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.735: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.735: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.735: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.735: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.736: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.736: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.736: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.736: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.737: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.737: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.738: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.738: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.738: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.738: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.738: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.738: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.739: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.739: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.739: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.739: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.739: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.740: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.740: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.743: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.743: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.743: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.743: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.743: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.744: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.744: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.744: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.745: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.745: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.745: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.745: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.746: variance_after = 2342 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.746: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.746: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.746: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.746: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.751: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.751: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.751: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.751: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.752: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.752: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.753: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.753: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.753: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.753: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.753: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.753: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.754: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.754: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.754: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.754: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.755: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.755: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.755: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.755: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.755: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.755: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.756: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.756: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.757: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.757: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.757: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.757: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.758: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.758: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.758: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.758: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.758: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.758: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.759: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.759: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.760: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.760: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.760: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.760: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.761: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.761: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.762: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.762: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.762: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.762: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.763: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.763: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.764: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.764: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.764: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.764: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.765: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.765: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.765: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.765: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.766: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.766: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.767: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.767: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.767: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.768: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.768: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.768: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.768: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.768: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.769: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.769: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.769: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.769: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.770: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.770: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.771: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.771: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.771: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.771: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.772: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.772: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.773: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.773: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.773: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.773: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.774: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.774: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.775: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.775: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.775: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.775: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.776: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.776: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.777: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.777: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.777: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.777: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.778: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.778: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.779: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.779: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.779: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.779: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.780: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.780: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.781: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.781: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.781: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.781: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.782: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.782: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.783: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.783: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.783: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.783: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.784: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.784: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.785: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.785: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.785: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.785: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.787: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.787: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.788: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.788: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.788: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.788: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.789: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.789: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.790: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.790: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.790: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.790: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.791: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.791: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.792: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.792: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.792: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.792: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.792: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.792: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.793: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.793: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.793: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.793: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.794: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.794: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.795: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.795: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.795: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.795: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.795: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.795: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.796: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.796: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.796: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.796: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.797: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.797: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.798: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.798: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.798: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.798: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.799: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.799: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.800: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.800: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.800: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.800: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.800: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.800: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.801: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.801: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.801: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.801: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.802: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.802: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.802: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.802: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.802: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.802: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.803: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.803: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.804: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.804: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.804: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.804: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.804: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.805: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.806: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.806: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.806: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.806: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.807: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.807: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.808: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.808: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.808: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.808: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.809: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.809: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.810: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.810: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.810: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.810: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.811: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.811: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.812: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.812: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.812: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.812: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.812: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.812: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.813: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.813: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.813: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.813: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.814: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.814: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.815: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.815: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.815: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.815: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.816: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.816: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.817: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.817: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.817: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.817: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.818: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.818: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.823: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.823: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.823: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.823: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.823: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.823: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.824: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.824: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.824: [vfs7552] QUERY DATA READY entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.824: Sending vfs7552_is_image_ready 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.825: [vfs7552] QUERY DATA READY entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.825: Receiving 64 bytes 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.826: Got 6 bytes out of 64 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.826: [vfs7552] QUERY DATA READY completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.826: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.826: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.826: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.826: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.826: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.827: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.827: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.827: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.828: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.828: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.835: [vfs7552] CAPTURE_NUM_STATES entering state 2 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.835: [vfs7552] REQUEST CHUNK entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.835: Sending vfs7552_read_image_chunk 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.836: [vfs7552] REQUEST CHUNK completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.836: [vfs7552] CAPTURE_NUM_STATES entering state 3 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.836: [vfs7552] CAPTURE_NUM_STATES entering state 4 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.837: Cleaning image 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.837: variance_after = 16 167s 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.837: [vfs7552] CAPTURE_NUM_STATES completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.837: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.847: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.847: [vfs7552] STOP CAPTURE entering state 0 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.847: Sending vfs7552_cmd_04 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.848: [vfs7552] STOP CAPTURE entering state 1 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.848: Receiving 64 bytes 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.848: [vfs7552] STOP CAPTURE entering state 2 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.848: Sending vfs7552_cmd_52 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.849: [vfs7552] STOP CAPTURE entering state 3 167s (process:3126): libfprint-vfs7552-DEBUG: 05:38:12.849: Receiving 64 bytes 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.850: [vfs7552] STOP CAPTURE completed successfully 167s (process:3126): libfprint-SSM-DEBUG: 05:38:12.850: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 167s (process:3126): libfprint-device-DEBUG: 05:38:12.850: Device reported finger status change: FP_FINGER_STATUS_NONE 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.850: Image device reported finger status: off 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.850: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.850: Deactivating image device 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.850: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.850: Image device deactivation completed 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.850: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 167s (process:3126): libfprint-device-DEBUG: 05:38:12.850: Device reported capture completion 167s (process:3126): libfprint-device-DEBUG: 05:38:12.850: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 167s (process:3126): libfprint-device-DEBUG: 05:38:12.850: Updated temperature model after 4.35 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 167s (process:3126): libfprint-image_device-DEBUG: 05:38:12.851: Image device close completed 167s (process:3126): libfprint-device-DEBUG: 05:38:12.851: Device reported close completion 167s (process:3126): libfprint-device-DEBUG: 05:38:12.851: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 167s (process:3126): libfprint-device-DEBUG: 05:38:12.851: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 167s ** (umockdev-run:3122): DEBUG: 05:38:12.969: umockdev.vala:154: Removing test bed /tmp/umockdev.A4HE22 167s (umockdev-run:3122): GLib-DEBUG: 05:38:12.977: unsetenv() is not thread-safe and should not be used after threads are created 168s Comparing PNGs /tmp/libfprint-umockdev-test-baukxdox/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 168s PASS: libfprint-2/driver-vfs7552.test 168s Running test: libfprint-2/driver-egismoc-0586.test 168s ** (umockdev-run:3135): DEBUG: 05:38:13.053: umockdev.vala:127: Created udev test bed /tmp/umockdev.LIAD22 168s ** (umockdev-run:3135): DEBUG: 05:38:13.053: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 168s ** (umockdev-run:3135): DEBUG: 05:38:13.055: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 168s ** (umockdev-run:3135): DEBUG: 05:38:13.059: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.LIAD22/dev/bus/usb/001/021 168s ** (umockdev-run:3135): DEBUG: 05:38:13.059: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 168s ** (umockdev-run:3135): DEBUG: 05:38:13.061: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 168s ** (umockdev-run:3135): DEBUG: 05:38:13.064: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.LIAD22/dev/bus/usb/001/001 168s ** (umockdev-run:3135): DEBUG: 05:38:13.064: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 168s ** (umockdev-run:3135): DEBUG: 05:38:13.065: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 168s (process:3139): libfprint-context-DEBUG: 05:38:13.160: Initializing FpContext (libfprint version 1.94.9+tod1) 168s (process:3139): libfprint-tod-DEBUG: 05:38:13.160: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 168s Executing: libfprint-2/driver-egismoc-0586.test 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.163: 114002471: ../libfprint/drivers/egismoc/egismoc.c:1597 168s (process:3139): libfprint-context-DEBUG: 05:38:13.163: No driver found for USB device 1D6B:0002 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.163: egismoc_probe enter --> 168s (process:3139): libfprint-device-DEBUG: 05:38:13.165: Device reported probe completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.165: Completing action FPI_DEVICE_ACTION_PROBE in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.166: Opening device 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.167: [egismoc] DEV_INIT_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.168: [egismoc] DEV_INIT_STATES entering state 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.168: [egismoc] DEV_INIT_STATES entering state 2 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.170: [egismoc] DEV_INIT_STATES entering state 3 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.170: [egismoc] DEV_INIT_STATES entering state 4 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.171: [egismoc] DEV_INIT_STATES entering state 5 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.171: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.171: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.171: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.172: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.173: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.173: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.173: Firmware version callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.173: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.173: Device firmware version is 9050.6.2.56 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.173: [egismoc] DEV_INIT_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.173: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.173: Device reported open completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.173: Completing action FPI_DEVICE_ACTION_OPEN in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.173: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.174: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.174: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.174: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.174: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.174: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.174: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.175: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.175: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.175: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.175: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.175: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.175: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.175: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.176: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.176: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.176: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.176: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.176: Clear storage 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.176: [egismoc] DELETE_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.176: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.176: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.176: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.177: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.178: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.178: [egismoc] DELETE_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: Get delete command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.178: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.178: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.179: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.180: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: Delete callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: Response prefix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.180: Device reported deletion completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.180: [egismoc] DELETE_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.180: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.180: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.180: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.180: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.180: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.181: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.182: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.182: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.182: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.182: Number of currently enrolled fingerprints on the device is 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.182: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.182: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.182: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.182: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.182: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3139): libfprint-device-DEBUG: 05:38:13.183: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.183: Enroll 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.183: [egismoc] ENROLL_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.183: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.183: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.183: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.184: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.184: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.185: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.185: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.185: Number of currently enrolled fingerprints on the device is 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.185: [egismoc] ENROLL_STATES entering state 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.185: [egismoc] ENROLL_STATES entering state 2 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.185: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.185: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.185: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.186: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.186: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.186: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.186: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.186: [egismoc] ENROLL_STATES entering state 3 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.186: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.186: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.186: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.187: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.188: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.188: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.188: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.188: [egismoc] ENROLL_STATES entering state 4 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.188: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.189: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.189: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.189: [egismoc] ENROLL_STATES entering state 5 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.189: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.189: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.189: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.190: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.191: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.191: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.191: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.191: [egismoc] ENROLL_STATES entering state 6 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.191: Get check command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.191: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.191: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.191: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.192: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.193: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.193: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.193: Enroll check callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.193: Response suffix valid: yes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.193: [egismoc] ENROLL_STATES entering state 7 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.193: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.193: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.193: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.193: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.194: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.194: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.194: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.194: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.194: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.194: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.194: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.195: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.196: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.196: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.196: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.196: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.196: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.196: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.196: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.196: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.197: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.197: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.197: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.197: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.197: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.198: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.198: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.198: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.198: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.198: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.198: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.198: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.199: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Partial capture successful. Please touch the sensor again (1/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.199: Device reported enroll progress, reported 1 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.199: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.199: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.199: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.200: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.201: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.201: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.201: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.201: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.201: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.201: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.201: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.202: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.203: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.203: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.203: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.203: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.203: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.203: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.204: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.204: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.204: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.204: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.204: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.204: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.207: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Partial capture successful. Please touch the sensor again (2/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.207: Device reported enroll progress, reported 2 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.207: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.207: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.207: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.208: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.208: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.208: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.209: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.209: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.209: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.209: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.209: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.209: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.211: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.211: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.211: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.211: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.211: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.211: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.212: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.212: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.212: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.212: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.212: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.212: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.212: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.213: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Partial capture successful. Please touch the sensor again (3/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.213: Device reported enroll progress, reported 3 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.213: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.213: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.213: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.214: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.215: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.215: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.215: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.215: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.215: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.215: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.215: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.216: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.217: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.217: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.217: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.217: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.217: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.217: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.218: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.218: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.218: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.218: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.218: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.218: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.219: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Partial capture successful. Please touch the sensor again (4/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.219: Device reported enroll progress, reported 4 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.219: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.219: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.219: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.221: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.221: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.221: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.221: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.222: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.222: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.222: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.222: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.222: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.223: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.223: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.223: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.223: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.223: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.224: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.224: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.224: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.224: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.224: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.224: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.224: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.225: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Partial capture successful. Please touch the sensor again (5/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.225: Device reported enroll progress, reported 5 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.225: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.225: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.225: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.226: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.227: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.227: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.227: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.227: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.227: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.227: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.227: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.227: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.228: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.228: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.228: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.228: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.228: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.229: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.229: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.229: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.229: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.229: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.229: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.230: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.231: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Partial capture successful. Please touch the sensor again (6/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.231: Device reported enroll progress, reported 6 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.231: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.231: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.231: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.231: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.232: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.232: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.232: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.232: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.232: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.232: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.232: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.233: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.234: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.234: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.234: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.234: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.234: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.234: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.234: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.235: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.235: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.235: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.235: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.235: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.236: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.236: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.236: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.236: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.236: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.236: Partial capture successful. Please touch the sensor again (7/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.236: Device reported enroll progress, reported 7 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.237: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.237: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.237: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.237: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.237: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.238: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.238: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.238: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.238: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.238: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.238: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.238: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.239: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.240: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.240: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.240: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.240: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.240: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.241: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.241: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.241: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.241: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.241: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.241: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.242: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.243: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Response suffix valid: NO 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Response suffix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.243: Device reported enroll progress, reported 7 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.243: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.243: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.243: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.243: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.244: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.244: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.245: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.245: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.245: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.245: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.245: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.245: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.246: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.246: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.246: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.246: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.246: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.247: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.247: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.247: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.247: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.247: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.247: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.248: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.249: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Partial capture successful. Please touch the sensor again (8/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.249: Device reported enroll progress, reported 8 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.249: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.249: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.249: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.250: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.251: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.251: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.251: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.251: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.251: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.251: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.251: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.252: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.252: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.252: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.252: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.252: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.252: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.252: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.253: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.253: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.253: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.253: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.253: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.253: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.254: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.255: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Response suffix valid: NO 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Response suffix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.255: Device reported enroll progress, reported 8 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.255: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.255: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.255: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.256: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.257: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.257: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.257: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.257: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.257: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.257: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.257: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.257: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.258: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.258: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.258: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.258: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.258: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.259: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.259: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.259: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.259: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.259: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.259: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.260: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.261: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Partial capture successful. Please touch the sensor again (9/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.261: Device reported enroll progress, reported 9 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.261: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.261: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.261: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.262: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.262: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.262: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.263: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.263: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.263: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.263: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.263: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.263: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.264: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.264: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.264: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.264: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.264: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.264: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.265: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.265: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.265: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.265: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.265: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.265: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.266: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.267: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Partial capture successful. Please touch the sensor again (10/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.267: Device reported enroll progress, reported 10 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.267: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.267: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.267: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.268: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.269: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.269: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.269: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.269: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.269: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.269: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.269: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.270: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.271: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.271: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.271: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.271: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.271: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.272: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.272: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.272: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.272: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.272: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.272: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.272: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.273: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Partial capture successful. Please touch the sensor again (11/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.273: Device reported enroll progress, reported 11 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.273: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.273: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.273: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.274: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.275: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.275: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.275: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.275: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.275: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.275: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.275: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.275: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.276: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.276: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.276: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.276: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.276: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.276: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.277: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.277: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.277: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.277: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.277: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.277: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.278: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.279: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Partial capture successful. Please touch the sensor again (12/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.279: Device reported enroll progress, reported 12 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.279: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.279: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.279: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.280: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.281: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.281: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.281: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.281: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.281: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.281: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.281: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.282: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.283: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.283: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.283: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.283: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.283: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.283: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.283: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.283: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.283: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.283: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.283: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.284: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.285: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.285: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Partial capture successful. Please touch the sensor again (13/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.285: Device reported enroll progress, reported 13 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.285: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.285: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.285: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.286: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.287: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.287: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.287: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.287: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.287: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.287: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.287: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.288: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.288: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.288: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.289: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.289: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.289: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.289: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.289: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.289: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.289: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.289: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.289: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.289: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.290: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.291: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Partial capture successful. Please touch the sensor again (14/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.291: Device reported enroll progress, reported 14 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.291: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.291: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.291: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.291: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.292: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.292: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.292: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.292: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.292: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.292: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.292: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.293: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.294: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.294: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.294: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.294: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.294: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.294: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.295: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.296: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.296: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.296: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.296: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.296: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.296: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.297: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Partial capture successful. Please touch the sensor again (15/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.297: Device reported enroll progress, reported 15 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.297: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.297: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.297: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.298: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.299: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.299: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.299: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.299: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.299: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.299: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.299: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.300: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.301: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.301: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.301: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.301: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.301: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.301: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.301: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.301: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.301: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.301: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.301: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.302: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.303: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Partial capture successful. Please touch the sensor again (16/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.303: Device reported enroll progress, reported 16 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.303: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.303: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.303: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.304: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.305: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.305: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.305: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.305: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.305: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.305: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.305: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.306: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.307: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.307: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.307: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.307: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.307: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.307: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.307: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.308: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.308: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.308: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.308: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.308: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.308: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.309: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.309: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.309: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.309: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.309: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.309: Partial capture successful. Please touch the sensor again (17/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.309: Device reported enroll progress, reported 17 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.310: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.310: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.310: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.310: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.310: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.311: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.311: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.311: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.311: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.311: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.311: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.311: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.312: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.313: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.313: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.313: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.313: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.313: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.313: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.314: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.314: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.314: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.314: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.314: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.314: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.315: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.316: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Partial capture successful. Please touch the sensor again (18/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.316: Device reported enroll progress, reported 18 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.316: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.316: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.316: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.317: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.317: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.317: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.318: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.318: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.318: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.318: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.318: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.318: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.319: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.319: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.319: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.319: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.319: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.319: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.320: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.320: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.320: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.320: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.320: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.320: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.320: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.321: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Partial capture successful. Please touch the sensor again (19/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.321: Device reported enroll progress, reported 19 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.321: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.321: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.322: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.322: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.323: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.323: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.323: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.323: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.323: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.323: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.323: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.324: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.325: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.325: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.325: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.325: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.325: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.325: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.325: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.325: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.325: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.325: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.325: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.326: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.327: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Partial capture successful. Please touch the sensor again (20/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.327: Device reported enroll progress, reported 20 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.327: [egismoc] ENROLL_STATES entering state 12 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.327: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.327: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.328: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.328: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.328: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.328: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.328: [egismoc] ENROLL_STATES entering state 13 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.328: New fingerprint ID: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.328: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.328: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.328: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.329: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.330: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.330: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.330: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.330: [egismoc] ENROLL_STATES entering state 14 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.330: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.330: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.330: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.331: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.331: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.331: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.331: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.331: [egismoc] ENROLL_STATES entering state 15 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.331: Enrollment was successful! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.331: Device reported enroll completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.331: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3139): libfprint-device-DEBUG: 05:38:13.331: Print for finger FP_FINGER_LEFT_INDEX enrolled 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.331: [egismoc] ENROLL_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.331: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.331: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.332: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.332: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.332: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.332: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.332: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.332: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.332: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.333: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.333: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.333: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.333: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.333: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.333: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.333: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.333: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.333: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.333: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.333: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-device-DEBUG: 05:38:13.334: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.334: Identify or Verify 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.334: [egismoc] IDENTIFY_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.334: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.334: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.334: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.335: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.336: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.336: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.336: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.336: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.336: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.336: [egismoc] IDENTIFY_STATES entering state 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.336: [egismoc] IDENTIFY_STATES entering state 2 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.336: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.336: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.336: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.337: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.337: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.338: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.338: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.338: [egismoc] IDENTIFY_STATES entering state 3 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.338: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.338: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.338: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.338: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.339: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.339: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.339: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.339: [egismoc] IDENTIFY_STATES entering state 4 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.339: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.340: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.340: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.340: [egismoc] IDENTIFY_STATES entering state 5 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.340: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.340: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.340: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.340: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.341: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.341: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.341: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.341: [egismoc] IDENTIFY_STATES entering state 6 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.341: Get check command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.341: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.341: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.341: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.342: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.343: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Identify check callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Identify successful for: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Verifying against: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-device-DEBUG: 05:38:13.343: Device reported verify result 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.343: [egismoc] IDENTIFY_STATES entering state 7 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.343: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.343: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.344: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.345: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.345: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.345: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.345: [egismoc] IDENTIFY_STATES entering state 8 168s (process:3139): libfprint-device-DEBUG: 05:38:13.345: Device reported verify completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.345: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.345: [egismoc] IDENTIFY_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.345: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.345: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.345: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-device-DEBUG: 05:38:13.345: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.345: Identify or Verify 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.345: [egismoc] IDENTIFY_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.345: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.345: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.345: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.346: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.347: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.347: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.347: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.347: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.347: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.347: [egismoc] IDENTIFY_STATES entering state 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.347: [egismoc] IDENTIFY_STATES entering state 2 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.347: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.347: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.347: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.348: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.349: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.349: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.349: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.349: [egismoc] IDENTIFY_STATES entering state 3 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.349: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.349: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.349: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.349: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.350: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.350: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.350: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.350: [egismoc] IDENTIFY_STATES entering state 4 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.350: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.350: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.351: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.351: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.351: [egismoc] IDENTIFY_STATES entering state 5 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.351: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.351: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.351: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.352: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.353: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.353: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.353: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.353: [egismoc] IDENTIFY_STATES entering state 6 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.353: Get check command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.353: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.353: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.353: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.353: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.354: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.354: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.354: Identify check callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.354: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.354: Identify successful for: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-device-DEBUG: 05:38:13.354: Device reported identify result 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.354: [egismoc] IDENTIFY_STATES entering state 7 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.354: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.354: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.354: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.355: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.356: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.356: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.356: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.356: [egismoc] IDENTIFY_STATES entering state 8 168s (process:3139): libfprint-device-DEBUG: 05:38:13.356: Device reported identify completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.356: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.356: [egismoc] IDENTIFY_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.356: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.356: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.356: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-device-DEBUG: 05:38:13.356: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.356: Enroll 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.356: [egismoc] ENROLL_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.356: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.356: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.356: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.357: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.358: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.358: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.358: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.358: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.358: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.358: [egismoc] ENROLL_STATES entering state 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.358: [egismoc] ENROLL_STATES entering state 2 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.358: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.358: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.358: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.359: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.359: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.359: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.359: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.359: [egismoc] ENROLL_STATES entering state 3 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.359: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.359: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.359: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.361: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.361: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.361: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.361: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.361: [egismoc] ENROLL_STATES entering state 4 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.361: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.361: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.362: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.362: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.362: [egismoc] ENROLL_STATES entering state 5 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.362: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.362: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.362: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.363: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.363: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.364: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.364: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.364: [egismoc] ENROLL_STATES entering state 6 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.364: Get check command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.364: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.364: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.364: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.364: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.365: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: Enroll check callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: Response suffix valid: NO 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.365: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.365: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.365: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 168s (process:3139): libfprint-device-DEBUG: 05:38:13.365: Device reported enroll completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.365: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3139): libfprint-device-DEBUG: 05:38:13.365: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.365: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.365: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.365: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.365: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.366: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.367: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.367: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.367: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.367: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.367: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.367: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-device-DEBUG: 05:38:13.367: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Enroll 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.367: [egismoc] ENROLL_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.367: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.367: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.368: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.369: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.369: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.369: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.369: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.369: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.369: [egismoc] ENROLL_STATES entering state 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.369: [egismoc] ENROLL_STATES entering state 2 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.369: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.369: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.369: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.370: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.370: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.370: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.370: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.371: [egismoc] ENROLL_STATES entering state 3 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.371: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.371: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.371: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.371: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.372: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.372: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.372: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.372: [egismoc] ENROLL_STATES entering state 4 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.372: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.372: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.373: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.373: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.373: [egismoc] ENROLL_STATES entering state 5 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.373: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.373: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.373: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.374: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.374: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.374: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.374: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.375: [egismoc] ENROLL_STATES entering state 6 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.375: Get check command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.375: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.375: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.375: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.375: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.376: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.376: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.376: Enroll check callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.376: Response suffix valid: yes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.376: [egismoc] ENROLL_STATES entering state 7 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.376: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.376: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.376: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.377: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.378: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.378: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.378: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.378: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.378: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.378: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.378: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.378: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.379: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.379: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.379: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.379: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.379: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.379: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.379: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.380: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.381: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.381: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.381: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.381: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.381: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.381: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.382: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.382: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.382: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.382: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.382: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.382: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.382: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.383: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Partial capture successful. Please touch the sensor again (1/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.383: Device reported enroll progress, reported 1 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.383: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.383: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.383: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.384: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.384: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.385: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.385: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.385: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.385: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.385: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.385: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.385: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.386: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.386: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.386: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.386: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.386: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.386: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.387: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.387: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.387: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.387: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.387: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.387: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.387: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.388: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Partial capture successful. Please touch the sensor again (2/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.388: Device reported enroll progress, reported 2 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.388: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.388: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.388: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.389: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.390: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.390: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.390: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.390: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.390: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.390: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.390: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.391: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.391: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.392: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.392: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.392: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.392: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.392: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.392: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.392: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.392: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.392: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.392: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.392: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.393: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.394: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Partial capture successful. Please touch the sensor again (3/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.394: Device reported enroll progress, reported 3 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.394: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.394: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.394: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.395: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.395: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.395: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.396: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.396: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.396: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.396: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.396: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.396: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.397: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.397: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.397: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.397: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.397: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.397: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.398: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.398: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.398: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.398: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.398: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.398: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.399: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.400: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Partial capture successful. Please touch the sensor again (4/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.400: Device reported enroll progress, reported 4 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.400: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.400: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.400: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.401: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.402: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.402: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.402: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.402: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.402: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.402: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.402: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.403: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.403: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.403: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.403: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.403: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.403: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.403: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.404: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.404: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.404: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.404: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.405: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.405: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.405: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.406: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Partial capture successful. Please touch the sensor again (5/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.406: Device reported enroll progress, reported 5 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.406: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.406: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.406: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.407: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.408: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.408: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.408: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.408: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.408: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.408: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.408: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.409: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.410: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.410: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.410: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.410: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.410: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.410: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.411: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.411: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.411: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.411: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.411: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.411: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.412: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.413: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Partial capture successful. Please touch the sensor again (6/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.413: Device reported enroll progress, reported 6 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.413: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.413: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.413: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.413: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.414: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.414: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.414: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.415: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.415: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.415: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.415: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.415: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.416: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.416: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.416: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.416: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.416: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.416: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.417: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.417: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.417: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.417: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.417: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.417: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.418: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.419: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Partial capture successful. Please touch the sensor again (7/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.419: Device reported enroll progress, reported 7 of 20 have been completed 168s listing - device should have prints 168s clear device storage 168s clear done 168s listing - device should be empty 168s enrolling 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 1, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 2, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 3, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 4, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 5, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 6, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 7, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 8, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 9, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 10, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 11, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 12, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 13, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 14, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 15, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 16, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 17, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 18, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 19, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 20, , None, None) 168s enroll done 168s listing - device should have 1 print 168s verifying 168s verify done 168s async identifying 168s indentification_done: 168s try to enroll duplicate 168s duplicate enroll attempt done 168s listing - device should still only have 1 print 168s enroll new finger 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 1, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 2, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 3, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 4, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 5, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 6, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 7, , None, None)(process:3139): libfprint-SSM-DEBUG: 05:38:13.419: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.419: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.419: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.420: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.421: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.421: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.421: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.421: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.421: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.421: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.421: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.422: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.423: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.423: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.423: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.423: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.423: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.423: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.424: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.424: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.424: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.424: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.424: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.424: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.425: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.426: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Response suffix valid: NO 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Response suffix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.426: Device reported enroll progress, reported 7 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.426: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.426: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.426: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.427: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.428: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.428: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.428: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.428: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.428: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.428: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.428: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.428: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.429: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.429: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.429: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.429: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.429: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.429: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.430: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.430: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.430: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.430: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.430: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.430: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.431: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.432: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Partial capture successful. Please touch the sensor again (8/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.432: Device reported enroll progress, reported 8 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.432: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.432: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.432: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.433: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.434: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.434: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.434: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.434: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.434: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.434: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.434: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.435: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.436: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.436: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.436: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.436: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.436: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.436: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.437: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.437: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.437: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.437: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.437: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.437: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.437: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.438: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Partial capture successful. Please touch the sensor again (9/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.438: Device reported enroll progress, reported 9 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.438: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.438: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.438: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.439: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.440: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.440: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.440: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.440: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.440: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.440: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.440: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.441: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.442: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.442: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.442: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.442: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.442: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.443: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.443: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.443: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.443: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.443: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.443: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.444: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.445: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Response suffix valid: NO 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Response suffix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.445: Device reported enroll progress, reported 9 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.445: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.445: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.445: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.446: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.447: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.447: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.447: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.447: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.447: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.447: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.447: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.447: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.448: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.448: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.448: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.448: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.448: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.449: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.449: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.449: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.449: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.449: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.449: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.450: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.451: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Partial capture successful. Please touch the sensor again (10/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.451: Device reported enroll progress, reported 10 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.451: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.451: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.451: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.452: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.453: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.453: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.453: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.453: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.453: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.453: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.453: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.454: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.454: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.454: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.454: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.454: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.454: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.455: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.455: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.455: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.455: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.455: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.455: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.456: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.457: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Partial capture successful. Please touch the sensor again (11/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.457: Device reported enroll progress, reported 11 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.457: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.457: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.457: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.458: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.459: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.459: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.459: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.459: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.459: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.459: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.459: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.459: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.460: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.460: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.460: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.460: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.460: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.460: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.461: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.461: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.461: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.461: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.461: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.461: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.462: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.463: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Partial capture successful. Please touch the sensor again (12/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.463: Device reported enroll progress, reported 12 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.463: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.463: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.463: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.464: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.465: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.465: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.465: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.465: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.465: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.465: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.465: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.466: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.467: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.467: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.467: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.467: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.467: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.467: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.468: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.468: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.468: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.468: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.468: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.468: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.469: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.469: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.469: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.470: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.470: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.470: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.470: Partial capture successful. Please touch the sensor again (13/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.470: Device reported enroll progress, reported 13 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.470: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.470: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.470: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.470: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.470: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.471: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.471: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.472: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.472: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.472: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.472: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.472: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.472: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.473: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.473: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.473: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.473: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.473: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.474: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.474: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.474: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.474: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.474: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.474: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.474: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.479: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.480: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Partial capture successful. Please touch the sensor again (14/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.480: Device reported enroll progress, reported 14 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.480: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.480: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.480: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.481: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.482: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.482: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.482: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.482: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.482: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.482: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.482: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.483: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.484: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.484: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.484: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.484: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.484: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.484: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.485: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.485: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.485: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.485: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.485: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.485: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.486: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.486: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.486: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.486: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.486: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.486: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.486: Partial capture successful. Please touch the sensor again (15/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.486: Device reported enroll progress, reported 15 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.487: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.487: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.487: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.487: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.487: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.488: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.488: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.489: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.489: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.489: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.489: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.489: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.489: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.490: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.490: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.490: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.490: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.490: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.490: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.491: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.491: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.491: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.491: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.491: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.491: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.492: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.493: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Partial capture successful. Please touch the sensor again (16/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.493: Device reported enroll progress, reported 16 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.493: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.493: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.493: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.494: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.495: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.495: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.495: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.495: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.495: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.495: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.495: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.496: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.496: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.496: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.496: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.496: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.496: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.497: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.497: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.497: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.497: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.497: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.497: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.498: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.499: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Partial capture successful. Please touch the sensor again (17/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.499: Device reported enroll progress, reported 17 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.499: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.499: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.499: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.500: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.501: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.501: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.501: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.501: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.501: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.501: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.501: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.502: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.503: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.503: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.503: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.503: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.503: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.504: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.504: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.504: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.504: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.504: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.504: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.504: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.505: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Partial capture successful. Please touch the sensor again (18/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.505: Device reported enroll progress, reported 18 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.505: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.505: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.505: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.506: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.507: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.507: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.507: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.507: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.507: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.507: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.507: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.508: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.509: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.509: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.509: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.509: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.509: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.510: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.510: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.510: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.510: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.510: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.510: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.511: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.512: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Partial capture successful. Please touch the sensor again (19/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.512: Device reported enroll progress, reported 19 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.512: [egismoc] ENROLL_STATES entering state 8 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.512: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.512: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.513: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.514: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.514: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.514: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.514: [egismoc] ENROLL_STATES entering state 9 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.514: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.514: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.514: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.515: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.516: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.516: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.516: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.516: [egismoc] ENROLL_STATES entering state 10 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.516: Wait for finger on sensor 168s (process:3139): libfprint-device-DEBUG: 05:38:13.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.517: Finger on sensor callback 168s (process:3139): libfprint-device-DEBUG: 05:38:13.517: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.517: [egismoc] ENROLL_STATES entering state 11 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.517: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.517: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.517: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.518: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.519: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Read capture callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Response prefix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Response suffix valid: yes 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Partial capture successful. Please touch the sensor again (20/20) 168s (process:3139): libfprint-device-DEBUG: 05:38:13.519: Device reported enroll progress, reported 20 of 20 have been completed 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.519: [egismoc] ENROLL_STATES entering state 12 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.519: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.519: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.520: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.521: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.521: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.521: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.521: [egismoc] ENROLL_STATES entering state 13 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.521: New fingerprint ID: FP1-00000000-7-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.521: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.521: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.521: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.522: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.522: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.523: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.523: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.523: [egismoc] ENROLL_STATES entering state 14 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.523: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.523: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.523: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.523: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.524: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.524: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.524: Task SSM next state callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.524: [egismoc] ENROLL_STATES entering state 15 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.524: Enrollment was successful! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.524: Device reported enroll completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.524: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3139): libfprint-device-DEBUG: 05:38:13.524: Print for finger FP_FINGER_RIGHT_INDEX enrolled 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.524: [egismoc] ENROLL_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.524: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.524: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.524: Updated temperature model after 0.16 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.524: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.524: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.524: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.525: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.525: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.525: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.526: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.526: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.526: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.526: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.526: Device fingerprint 2: FP1-00000000-7-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.526: Number of currently enrolled fingerprints on the device is 2 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.526: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.526: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.526: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.526: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.526: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.526: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.527: Delete 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.527: [egismoc] DELETE_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.527: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.527: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.527: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.528: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.528: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.529: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Device fingerprint 2: FP1-00000000-7-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Number of currently enrolled fingerprints on the device is 2 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.529: [egismoc] DELETE_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Get delete command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.529: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.529: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.530: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.531: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: Delete callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: Response prefix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.531: Device reported deletion completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.531: [egismoc] DELETE_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.531: Completing action FPI_DEVICE_ACTION_DELETE in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.531: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.531: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.531: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.531: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.532: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.533: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Device fingerprint 1: FP1-00000000-7-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.533: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.533: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.533: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.533: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.533: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Clear storage 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.533: [egismoc] DELETE_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.533: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.533: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.534: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.535: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: Device fingerprint 1: FP1-00000000-7-00000000-nobody 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: Number of currently enrolled fingerprints on the device is 1 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.535: [egismoc] DELETE_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: Get delete command 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.535: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.535: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.536: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.537: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: Delete callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: Response prefix valid: yes 168s (process:3139): libfprint-device-DEBUG: 05:38:13.537: Device reported deletion completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.537: [egismoc] DELETE_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.537: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.537: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: List 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.537: [egismoc] LIST_STATES entering state 0 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: Execute command and get response 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.537: Get check bytes 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.537: [egismoc] CMD_STATES entering state 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.538: [egismoc] CMD_STATES entering state 1 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.539: Command receive callback 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.539: [egismoc] CMD_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.539: List callback 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.539: Number of currently enrolled fingerprints on the device is 0 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.539: [egismoc] LIST_STATES entering state 1 168s (process:3139): libfprint-device-DEBUG: 05:38:13.539: Device reported listing completion 168s (process:3139): libfprint-SSM-DEBUG: 05:38:13.539: [egismoc] LIST_STATES completed successfully 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.539: Task SSM done 168s (process:3139): libfprint-device-DEBUG: 05:38:13.539: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.539: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.540: Closing device 168s (process:3139): libfprint-egismoc-DEBUG: 05:38:13.540: Cancel 168s (process:3139): libfprint-device-DEBUG: 05:38:13.540: Device reported close completion 168s (process:3139): libfprint-device-DEBUG: 05:38:13.540: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 168s (process:3139): libfprint-device-DEBUG: 05:38:13.540: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 8, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 9, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 10, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 11, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 12, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 13, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 14, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 15, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 16, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 17, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 18, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 19, , None, None) 168s finger status: 168s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x70572668e080 (FpiDeviceEgisMoc at 0x38757a20)>, 20, , None, None) 168s enroll new finger done 168s listing - device should have 2 prints 168s deleting first print 168s delete done 168s listing - device should only have second print 168s clear device storage 168s clear done 168s listing - device should be empty 168s ** (umockdev-run:3135): DEBUG: 05:38:13.565: umockdev.vala:154: Removing test bed /tmp/umockdev.LIAD22 168s (umockdev-run:3135): GLib-DEBUG: 05:38:13.576: unsetenv() is not thread-safe and should not be used after threads are created 168s PASS: libfprint-2/driver-egismoc-0586.test 168s Running test: libfprint-2/driver-egismoc-05a1.test 168s ** (umockdev-run:3147): DEBUG: 05:38:13.651: umockdev.vala:127: Created udev test bed /tmp/umockdev.K1G012 168s ** (umockdev-run:3147): DEBUG: 05:38:13.651: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 168s ** (umockdev-run:3147): DEBUG: 05:38:13.653: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 168s ** (umockdev-run:3147): DEBUG: 05:38:13.657: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.K1G012/dev/bus/usb/001/003 168s ** (umockdev-run:3147): DEBUG: 05:38:13.658: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 168s ** (umockdev-run:3147): DEBUG: 05:38:13.659: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 168s ** (umockdev-run:3147): DEBUG: 05:38:13.662: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.K1G012/dev/bus/usb/001/001 168s ** (umockdev-run:3147): DEBUG: 05:38:13.662: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 168s ** (umockdev-run:3147): DEBUG: 05:38:13.663: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 168s (process:3151): libfprint-context-DEBUG: 05:38:13.769: Initializing FpContext (libfprint version 1.94.9+tod1) 168s (process:3151): libfprint-tod-DEBUG: 05:38:13.769: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.771: 114611390: ../libfprint/drivers/egismoc/egismoc.c:1597 168s (process:3151): libfprint-context-DEBUG: 05:38:13.772: No driver found for USB device 1D6B:0002 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.772: egismoc_probe enter --> 168s (process:3151): libfprint-device-DEBUG: 05:38:13.774: Device reported probe completion 168s (process:3151): libfprint-device-DEBUG: 05:38:13.774: Completing action FPI_DEVICE_ACTION_PROBE in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.774: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.776: Opening device 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.776: [egismoc] DEV_INIT_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.778: [egismoc] DEV_INIT_STATES entering state 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.779: [egismoc] DEV_INIT_STATES entering state 2 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.780: [egismoc] DEV_INIT_STATES entering state 3 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.781: [egismoc] DEV_INIT_STATES entering state 4 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.782: [egismoc] DEV_INIT_STATES entering state 5 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.782: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.782: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.782: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.783: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.784: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.784: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.784: Firmware version callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.784: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.784: Device firmware version is 9050.1.2.13 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.784: [egismoc] DEV_INIT_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.784: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.784: Device reported open completion 168s (process:3151): libfprint-device-DEBUG: 05:38:13.784: Completing action FPI_DEVICE_ACTION_OPEN in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.784: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.785: List 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.785: [egismoc] LIST_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.785: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.785: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.785: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.786: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.787: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Number of currently enrolled fingerprints on the device is 3 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.787: [egismoc] LIST_STATES entering state 1 168s (process:3151): libfprint-device-DEBUG: 05:38:13.787: Device reported listing completion 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.787: [egismoc] LIST_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.787: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.787: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Clear storage 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.787: [egismoc] DELETE_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.787: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.787: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.788: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.789: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Number of currently enrolled fingerprints on the device is 3 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.789: [egismoc] DELETE_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Get delete command 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.789: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.789: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.790: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.791: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: Delete callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: Response prefix valid: yes 168s (process:3151): libfprint-device-DEBUG: 05:38:13.791: Device reported deletion completion 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.791: [egismoc] DELETE_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.791: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.791: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: List 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.791: [egismoc] LIST_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.791: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.791: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.792: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.793: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.793: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.793: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.793: Number of currently enrolled fingerprints on the device is 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.793: [egismoc] LIST_STATES entering state 1 168s (process:3151): libfprint-device-DEBUG: 05:38:13.793: Device reported listing completion 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.793: [egismoc] LIST_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.793: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.793: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.793: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3151): libfprint-device-DEBUG: 05:38:13.794: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.794: Enroll 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.795: [egismoc] ENROLL_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.795: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.795: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.795: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.795: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.797: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.797: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.797: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.797: Number of currently enrolled fingerprints on the device is 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.797: [egismoc] ENROLL_STATES entering state 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.797: [egismoc] ENROLL_STATES entering state 2 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.797: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.797: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.797: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.797: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.798: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.798: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.798: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.798: [egismoc] ENROLL_STATES entering state 3 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.798: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.799: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.799: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.799: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.800: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.800: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.800: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.800: [egismoc] ENROLL_STATES entering state 4 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.800: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.801: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.801: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.801: [egismoc] ENROLL_STATES entering state 5 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.801: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.801: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.801: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.802: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.803: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.803: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.803: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.803: [egismoc] ENROLL_STATES entering state 6 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.803: Get check command 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.803: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.803: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.803: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.804: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.805: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.805: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.805: Enroll check callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.805: Response suffix valid: yes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.805: [egismoc] ENROLL_STATES entering state 7 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.805: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.805: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.805: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.806: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.807: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.807: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.807: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.807: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.807: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.807: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.807: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.808: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.809: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.809: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.809: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.809: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.809: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.809: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.809: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.810: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.815: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.815: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.815: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.815: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.815: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.815: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.816: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.816: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.816: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.816: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.816: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.816: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.817: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.818: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Partial capture successful. Please touch the sensor again (1/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.818: Device reported enroll progress, reported 1 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.818: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.818: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.818: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.819: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.820: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.820: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.820: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.820: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.820: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.820: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.820: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.821: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.822: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.822: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.822: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.822: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.822: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.822: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.823: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.823: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.823: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.823: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.823: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.823: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.824: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.824: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.824: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.824: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.824: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.824: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.824: Partial capture successful. Please touch the sensor again (2/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.824: Device reported enroll progress, reported 2 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.825: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.825: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.825: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.825: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.825: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.827: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.827: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.827: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.827: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.827: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.827: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.827: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.828: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.828: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.828: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.828: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.828: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.828: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.828: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.829: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.829: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.829: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.829: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.829: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.829: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.830: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.830: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.830: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.831: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.831: Response prefix valid: NO 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.831: Response prefix valid: NO 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.831: Response prefix valid: yes 168s (process:3151): libfprint-device-DEBUG: 05:38:13.831: Device reported enroll progress, reported 2 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.831: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.831: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.831: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.831: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.831: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.832: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.832: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.832: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.832: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.832: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.832: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.832: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.833: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.834: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.834: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.834: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.834: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.834: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.834: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.835: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.835: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.835: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.835: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.835: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.835: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.835: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.836: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Partial capture successful. Please touch the sensor again (3/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.836: Device reported enroll progress, reported 3 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.836: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.836: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.836: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.837: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.838: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.838: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.838: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.838: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.838: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.838: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.838: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.838: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.839: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.839: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.839: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.839: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.839: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.840: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.840: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.840: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.840: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.840: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.840: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.841: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.841: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.842: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.842: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.842: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.842: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.842: Partial capture successful. Please touch the sensor again (4/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.842: Device reported enroll progress, reported 4 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.842: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.842: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.842: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.842: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.842: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.843: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.843: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.843: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.843: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.843: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.843: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.843: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.844: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.845: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.845: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.845: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.845: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.845: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.846: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.846: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.846: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.846: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.846: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.846: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.846: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.847: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Partial capture successful. Please touch the sensor again (5/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.847: Device reported enroll progress, reported 5 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.847: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.847: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.847: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.848: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.849: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.849: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.849: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.849: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.849: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.849: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.849: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.849: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.850: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.850: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.850: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.850: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.850: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.851: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.851: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.851: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.851: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.851: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.851: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.851: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.852: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Partial capture successful. Please touch the sensor again (6/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.852: Device reported enroll progress, reported 6 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.852: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.852: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.852: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.853: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.853: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.853: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.853: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.853: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.853: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.853: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.853: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.854: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.855: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.855: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.855: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.855: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.855: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.855: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.855: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.855: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.855: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.855: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.855: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.856: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.857: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Partial capture successful. Please touch the sensor again (7/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.857: Device reported enroll progress, reported 7 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.857: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.857: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.857: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.858: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.858: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.858: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.858: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.858: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.858: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.858: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.858: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.859: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.860: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.860: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.860: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.860: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.860: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.861: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.861: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.861: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.861: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.861: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.861: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.863: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.863: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Partial capture successful. Please touch the sensor again (8/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.863: Device reported enroll progress, reported 8 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.863: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.863: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.863: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.864: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.865: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.865: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.865: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.865: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.865: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.865: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.865: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.865: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.866: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.866: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.866: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.866: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.866: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.867: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.867: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.867: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.867: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.867: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.867: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.868: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.868: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.868: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.868: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.868: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.868: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.868: Partial capture successful. Please touch the sensor again (9/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.868: Device reported enroll progress, reported 9 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.868: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.869: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.869: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.869: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.869: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.870: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.870: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.870: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.870: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.870: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.870: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.870: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.871: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.871: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.871: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.871: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.871: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.871: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.872: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.872: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.872: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.872: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.872: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.872: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.873: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.873: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.873: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.873: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.874: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.874: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.874: Partial capture successful. Please touch the sensor again (10/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.874: Device reported enroll progress, reported 10 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.874: [egismoc] ENROLL_STATES entering state 12 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.874: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.874: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.874: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.875: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.875: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.875: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.875: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.875: [egismoc] ENROLL_STATES entering state 13 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.875: New fingerprint ID: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.875: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.875: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.875: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.876: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.879: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.879: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.879: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.879: [egismoc] ENROLL_STATES entering state 14 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.879: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.879: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.879: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.880: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.880: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.880: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.880: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.880: [egismoc] ENROLL_STATES entering state 15 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.880: Enrollment was successful! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.880: Device reported enroll completion 168s (process:3151): libfprint-device-DEBUG: 05:38:13.880: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3151): libfprint-device-DEBUG: 05:38:13.880: Print for finger FP_FINGER_LEFT_INDEX enrolled 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.881: [egismoc] ENROLL_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.881: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.881: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.881: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.881: List 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.881: [egismoc] LIST_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.881: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.881: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.881: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.881: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.882: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.882: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.882: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.882: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.882: Number of currently enrolled fingerprints on the device is 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.882: [egismoc] LIST_STATES entering state 1 168s (process:3151): libfprint-device-DEBUG: 05:38:13.882: Device reported listing completion 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.882: [egismoc] LIST_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.882: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.882: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.882: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-device-DEBUG: 05:38:13.883: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.883: Identify or Verify 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.883: [egismoc] IDENTIFY_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.883: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.883: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.883: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.883: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.887: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.887: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.887: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.887: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.887: Number of currently enrolled fingerprints on the device is 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.887: [egismoc] IDENTIFY_STATES entering state 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.887: [egismoc] IDENTIFY_STATES entering state 2 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.887: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.887: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.887: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.887: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.888: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.888: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.888: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.888: [egismoc] IDENTIFY_STATES entering state 3 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.888: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.888: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.888: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.889: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.889: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.889: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.889: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.889: [egismoc] IDENTIFY_STATES entering state 4 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.889: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.889: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.890: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.890: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.890: [egismoc] IDENTIFY_STATES entering state 5 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.890: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.890: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.890: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.891: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.891: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.891: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.891: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.891: [egismoc] IDENTIFY_STATES entering state 6 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.891: Get check command 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.891: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.891: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.891: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.892: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.893: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Identify check callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Identify successful for: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Verifying against: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-device-DEBUG: 05:38:13.893: Device reported verify result 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.893: [egismoc] IDENTIFY_STATES entering state 7 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.893: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.893: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.894: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.894: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.894: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.894: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.894: [egismoc] IDENTIFY_STATES entering state 8 168s (process:3151): libfprint-device-DEBUG: 05:38:13.894: Device reported verify completion 168s (process:3151): libfprint-device-DEBUG: 05:38:13.894: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.894: [egismoc] IDENTIFY_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.894: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.894: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.894: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-device-DEBUG: 05:38:13.896: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.896: Identify or Verify 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.896: [egismoc] IDENTIFY_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.896: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.896: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.896: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.896: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.897: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.897: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.897: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.897: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.897: Number of currently enrolled fingerprints on the device is 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.897: [egismoc] IDENTIFY_STATES entering state 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.897: [egismoc] IDENTIFY_STATES entering state 2 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.897: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.897: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.897: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.898: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.898: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.898: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.898: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.898: [egismoc] IDENTIFY_STATES entering state 3 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.898: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.898: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.898: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.899: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.900: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.900: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.900: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.900: [egismoc] IDENTIFY_STATES entering state 4 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.900: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.901: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.901: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.901: [egismoc] IDENTIFY_STATES entering state 5 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.901: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.901: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.901: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.901: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.902: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.902: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.902: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.902: [egismoc] IDENTIFY_STATES entering state 6 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.902: Get check command 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.902: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.902: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.902: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.903: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.903: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.903: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.903: Identify check callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.903: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.903: Identify successful for: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-device-DEBUG: 05:38:13.904: Device reported identify result 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.904: [egismoc] IDENTIFY_STATES entering state 7 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.904: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.904: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.904: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.904: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.905: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.905: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.905: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.905: [egismoc] IDENTIFY_STATES entering state 8 168s (process:3151): libfprint-device-DEBUG: 05:38:13.905: Device reported identify completion 168s (process:3151): libfprint-device-DEBUG: 05:38:13.905: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.905: [egismoc] IDENTIFY_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.905: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.905: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.905: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-device-DEBUG: 05:38:13.906: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.906: Enroll 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.906: [egismoc] ENROLL_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.906: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.906: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.906: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.907: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.908: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.908: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.908: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.908: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.908: Number of currently enrolled fingerprints on the device is 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.908: [egismoc] ENROLL_STATES entering state 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.908: [egismoc] ENROLL_STATES entering state 2 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.908: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.908: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.908: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.909: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.909: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.909: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.909: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.909: [egismoc] ENROLL_STATES entering state 3 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.909: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.909: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.910: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.910: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.911: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.911: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.911: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.911: [egismoc] ENROLL_STATES entering state 4 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.911: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.912: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.912: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.912: [egismoc] ENROLL_STATES entering state 5 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.912: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.912: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.912: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.913: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.913: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.913: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.913: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.913: [egismoc] ENROLL_STATES entering state 6 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.913: Get check command 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.913: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.913: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.913: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.914: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.915: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: Enroll check callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: Response suffix valid: NO 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.915: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.915: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.915: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 168s (process:3151): libfprint-device-DEBUG: 05:38:13.915: Device reported enroll completion 168s (process:3151): libfprint-device-DEBUG: 05:38:13.915: Device reported finger status change: FP_FINGER_STATUS_NONE 168s (process:3151): libfprint-device-DEBUG: 05:38:13.915: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.915: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: List 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.915: [egismoc] LIST_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.915: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.915: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.916: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.917: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Number of currently enrolled fingerprints on the device is 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.917: [egismoc] LIST_STATES entering state 1 168s (process:3151): libfprint-device-DEBUG: 05:38:13.917: Device reported listing completion 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.917: [egismoc] LIST_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Task SSM done 168s (process:3151): libfprint-device-DEBUG: 05:38:13.917: Completing action FPI_DEVICE_ACTION_LIST in idle! 168s (process:3151): libfprint-device-DEBUG: 05:38:13.917: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-device-DEBUG: 05:38:13.917: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Enroll 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.917: [egismoc] ENROLL_STATES entering state 0 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.917: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.917: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.918: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.918: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.918: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.918: List callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.918: Device fingerprint 1: FP1-00000000-2-00000000-nobody 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.918: Number of currently enrolled fingerprints on the device is 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.918: [egismoc] ENROLL_STATES entering state 1 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.919: [egismoc] ENROLL_STATES entering state 2 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.919: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.919: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.919: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.919: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.920: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.920: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.920: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.920: [egismoc] ENROLL_STATES entering state 3 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.920: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.920: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.920: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.921: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.923: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.923: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.923: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.923: [egismoc] ENROLL_STATES entering state 4 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.923: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.923: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.927: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.927: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.927: [egismoc] ENROLL_STATES entering state 5 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.927: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.927: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.927: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.928: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.929: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.929: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.929: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.929: [egismoc] ENROLL_STATES entering state 6 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.929: Get check command 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.929: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.929: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.929: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.930: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.931: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.931: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.931: Enroll check callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.931: Response suffix valid: yes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.931: [egismoc] ENROLL_STATES entering state 7 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.931: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.931: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.931: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.931: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.932: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.932: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.932: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.932: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.932: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.932: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.932: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.933: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.934: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.934: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.934: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.934: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.934: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.934: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.934: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.934: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.935: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.935: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.935: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.935: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.935: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.935: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.936: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.936: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.936: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.936: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.936: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.936: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.937: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.938: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Partial capture successful. Please touch the sensor again (1/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.938: Device reported enroll progress, reported 1 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.938: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.938: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.938: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.938: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.939: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.939: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.939: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.939: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.939: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.939: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.939: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.940: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.941: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.941: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.941: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.941: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.941: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.942: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.942: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.942: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.942: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.942: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.942: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.942: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.943: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Partial capture successful. Please touch the sensor again (2/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.943: Device reported enroll progress, reported 2 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.943: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.943: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.943: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.944: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.945: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.945: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.945: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.945: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.945: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.945: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.945: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.946: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.946: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.946: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.946: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.946: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.946: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.947: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.947: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.947: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.947: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.947: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.947: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.948: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.949: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Response suffix valid: NO 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Response suffix valid: yes 168s (process:3151): libfprint-device-DEBUG: 05:38:13.949: Device reported enroll progress, reported 2 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.949: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.949: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.949: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.950: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.950: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.950: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.950: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.950: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.950: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.950: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.950: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.951: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.952: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.952: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.952: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.952: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.952: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.952: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.953: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.953: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.953: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.953: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.953: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.953: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.954: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.955: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Response suffix valid: NO 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Response suffix valid: yes 168s (process:3151): libfprint-device-DEBUG: 05:38:13.955: Device reported enroll progress, reported 2 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.955: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.955: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.955: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.956: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.957: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.957: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.957: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.957: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.957: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.957: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.957: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.958: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.959: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.959: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.959: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.959: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.959: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.959: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.959: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.959: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.959: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.959: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.959: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.959: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.960: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.961: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Partial capture successful. Please touch the sensor again (3/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.961: Device reported enroll progress, reported 3 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.961: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.961: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.961: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.962: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.962: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.962: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.962: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.963: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.963: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.963: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.963: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.963: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.965: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.965: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.965: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.965: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.965: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.966: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.966: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.966: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.966: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.966: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.966: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.967: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.967: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.967: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.967: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.967: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.967: Response suffix valid: NO 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.967: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.967: Response suffix valid: yes 168s (process:3151): libfprint-device-DEBUG: 05:38:13.967: Device reported enroll progress, reported 3 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.968: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.968: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.968: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.968: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.968: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.969: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.969: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.969: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.969: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.969: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.969: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.969: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.970: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.971: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.971: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.971: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.971: [egismoc] ENROLL_STATES entering state 10 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.971: Wait for finger on sensor 168s (process:3151): libfprint-device-DEBUG: 05:38:13.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.972: Finger on sensor callback 168s (process:3151): libfprint-device-DEBUG: 05:38:13.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.972: [egismoc] ENROLL_STATES entering state 11 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.972: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.972: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.972: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.972: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.974: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Read capture callback 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Response prefix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Response suffix valid: yes 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Partial capture successful. Please touch the sensor again (4/10) 168s (process:3151): libfprint-device-DEBUG: 05:38:13.974: Device reported enroll progress, reported 4 of 10 have been completed 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.974: [egismoc] ENROLL_STATES entering state 8 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.974: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.974: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.975: [egismoc] CMD_STATES entering state 1 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.976: Command receive callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.976: [egismoc] CMD_STATES completed successfully 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.976: Task SSM next state callback 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.976: [egismoc] ENROLL_STATES entering state 9 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.976: Execute command and get response 168s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.976: Get check bytes 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.976: [egismoc] CMD_STATES entering state 0 168s (process:3151): libfprint-SSM-DEBUG: 05:38:13.977: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.979: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.979: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.979: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.979: [egismoc] ENROLL_STATES entering state 10 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.979: Wait for finger on sensor 169s (process:3151): libfprint-device-DEBUG: 05:38:13.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.980: Finger on sensor callback 169s (process:3151): libfprint-device-DEBUG: 05:38:13.980: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.980: [egismoc] ENROLL_STATES entering state 11 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.980: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.980: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.980: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.982: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.983: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Read capture callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Response prefix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Response suffix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Partial capture successful. Please touch the sensor again (5/10) 169s (process:3151): libfprint-device-DEBUG: 05:38:13.983: Device reported enroll progress, reported 5 of 10 have been completed 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.983: [egismoc] ENROLL_STATES entering state 8 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.983: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.983: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.984: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.985: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.985: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.985: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.985: [egismoc] ENROLL_STATES entering state 9 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.985: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.985: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.985: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.986: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.988: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.988: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.988: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.988: [egismoc] ENROLL_STATES entering state 10 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.988: Wait for finger on sensor 169s (process:3151): libfprint-device-DEBUG: 05:38:13.988: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.989: Finger on sensor callback 169s (process:3151): libfprint-device-DEBUG: 05:38:13.989: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.989: [egismoc] ENROLL_STATES entering state 11 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.989: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.989: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.989: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.990: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.991: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Read capture callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Response prefix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Response suffix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Partial capture successful. Please touch the sensor again (6/10) 169s (process:3151): libfprint-device-DEBUG: 05:38:13.991: Device reported enroll progress, reported 6 of 10 have been completed 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.991: [egismoc] ENROLL_STATES entering state 8 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.991: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.991: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.992: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.993: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.993: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.993: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.994: [egismoc] ENROLL_STATES entering state 9 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.994: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.994: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.994: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.994: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.995: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.996: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.996: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.996: [egismoc] ENROLL_STATES entering state 10 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.996: Wait for finger on sensor 169s (process:3151): libfprint-device-DEBUG: 05:38:13.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.997: Finger on sensor callback 169s (process:3151): libfprint-device-DEBUG: 05:38:13.997: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.997: [egismoc] ENROLL_STATES entering state 11 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.997: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.997: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.997: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.998: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.999: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Read capture callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Response prefix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Response suffix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Partial capture successful. Please touch the sensor again (7/10) 169s (process:3151): libfprint-device-DEBUG: 05:38:13.999: Device reported enroll progress, reported 7 of 10 have been completed 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.999: [egismoc] ENROLL_STATES entering state 8 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:13.999: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:13.999: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.000: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.001: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.001: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.001: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.001: [egismoc] ENROLL_STATES entering state 9 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.001: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.001: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.001: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.002: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.003: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.003: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.003: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.003: [egismoc] ENROLL_STATES entering state 10 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.003: Wait for finger on sensor 169s (process:3151): libfprint-device-DEBUG: 05:38:14.003: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.004: Finger on sensor callback 169s (process:3151): libfprint-device-DEBUG: 05:38:14.004: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.004: [egismoc] ENROLL_STATES entering state 11 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.004: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.004: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.004: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.005: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.006: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.006: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.006: Read capture callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.006: Response prefix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.006: Response suffix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.006: Partial capture successful. Please touch the sensor again (8/10) 169s (process:3151): libfprint-device-DEBUG: 05:38:14.006: Device reported enroll progress, reported 8 of 10 have been completed 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.006: [egismoc] ENROLL_STATES entering state 8 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.007: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.007: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.007: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.007: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.008: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.008: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.008: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.008: [egismoc] ENROLL_STATES entering state 9 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.008: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.008: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.008: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.009: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.010: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.010: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.010: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.010: [egismoc] ENROLL_STATES entering state 10 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.010: Wait for finger on sensor 169s (process:3151): libfprint-device-DEBUG: 05:38:14.010: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.010: Finger on sensor callback 169s (process:3151): libfprint-device-DEBUG: 05:38:14.011: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.011: [egismoc] ENROLL_STATES entering state 11 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.011: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.011: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.011: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.011: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.012: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Read capture callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Response prefix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Response suffix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Partial capture successful. Please touch the sensor again (9/10) 169s (process:3151): libfprint-device-DEBUG: 05:38:14.012: Device reported enroll progress, reported 9 of 10 have been completed 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.012: [egismoc] ENROLL_STATES entering state 8 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.012: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.012: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.013: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.014: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.014: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.014: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.014: [egismoc] ENROLL_STATES entering state 9 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.014: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.014: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.014: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.015: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.015: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.015: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.015: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.015: [egismoc] ENROLL_STATES entering state 10 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.015: Wait for finger on sensor 169s (process:3151): libfprint-device-DEBUG: 05:38:14.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.016: Finger on sensor callback 169s (process:3151): libfprint-device-DEBUG: 05:38:14.016: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.016: [egismoc] ENROLL_STATES entering state 11 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.016: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.016: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.016: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.017: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.018: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Read capture callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Response prefix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Response suffix valid: yes 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Partial capture successful. Please touch the sensor again (10/10) 169s (process:3151): libfprint-device-DEBUG: 05:38:14.018: Device reported enroll progress, reported 10 of 10 have been completed 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.018: [egismoc] ENROLL_STATES entering state 12 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.018: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.018: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.018: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.019: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.019: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.019: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.019: [egismoc] ENROLL_STATES entering state 13 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.019: New fingerprint ID: FP1-00000000-7-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.019: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.019: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.019: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.020: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.021: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.021: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.021: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.021: [egismoc] ENROLL_STATES entering state 14 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.021: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.021: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.021: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.021: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.022: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: Task SSM next state callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.022: [egismoc] ENROLL_STATES entering state 15 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: Enrollment was successful! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.022: Device reported enroll completion 169s (process:3151): libfprint-device-DEBUG: 05:38:14.022: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3151): libfprint-device-DEBUG: 05:38:14.022: Print for finger FP_FINGER_RIGHT_INDEX enrolled 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.022: [egismoc] ENROLL_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: Task SSM done 169s (process:3151): libfprint-device-DEBUG: 05:38:14.022: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.022: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: List 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.022: [egismoc] LIST_STATES entering state 0 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.022: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.022: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.023: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.024: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.024: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.024: List callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.024: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.024: Device fingerprint 2: FP1-00000000-7-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.024: Number of currently enrolled fingerprints on the device is 2 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.024: [egismoc] LIST_STATES entering state 1 169s (process:3151): libfprint-device-DEBUG: 05:38:14.024: Device reported listing completion 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.024: [egismoc] LIST_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.024: Task SSM done 169s (process:3151): libfprint-device-DEBUG: 05:38:14.024: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.024: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.025: Delete 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.025: [egismoc] DELETE_STATES entering state 0 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.025: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.025: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.025: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.025: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.026: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: List callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Device fingerprint 2: FP1-00000000-7-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Number of currently enrolled fingerprints on the device is 2 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.026: [egismoc] DELETE_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Get delete command 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.026: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.026: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.027: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.027: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.027: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.027: Delete callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.028: Response prefix valid: yes 169s (process:3151): libfprint-device-DEBUG: 05:38:14.028: Device reported deletion completion 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.028: [egismoc] DELETE_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.028: Task SSM done 169s (process:3151): libfprint-device-DEBUG: 05:38:14.028: Completing action FPI_DEVICE_ACTION_DELETE in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.028: List 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.028: [egismoc] LIST_STATES entering state 0 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.028: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.028: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.028: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.031: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.032: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: List callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Device fingerprint 1: FP1-00000000-7-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Number of currently enrolled fingerprints on the device is 1 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.032: [egismoc] LIST_STATES entering state 1 169s (process:3151): libfprint-device-DEBUG: 05:38:14.032: Device reported listing completion 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.032: [egismoc] LIST_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Task SSM done 169s (process:3151): libfprint-device-DEBUG: 05:38:14.032: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.032: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Clear storage 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.032: [egismoc] DELETE_STATES entering state 0 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.032: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.032: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.033: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.034: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.034: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.034: List callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.034: Device fingerprint 1: FP1-00000000-7-00000000-nobody 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.034: Number of currently enrolled fingerprints on the device is 1 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.034: [egismoc] DELETE_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.035: Get delete command 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.035: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.035: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.035: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.035: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.036: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: Delete callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: Response prefix valid: yes 169s (process:3151): libfprint-device-DEBUG: 05:38:14.036: Device reported deletion completion 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.036: [egismoc] DELETE_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: Task SSM done 169s (process:3151): libfprint-device-DEBUG: 05:38:14.036: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.036: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: List 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.036: [egismoc] LIST_STATES entering state 0 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: Execute command and get response 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.036: Get check bytes 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.036: [egismoc] CMD_STATES entering state 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.037: [egismoc] CMD_STATES entering state 1 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.038: Command receive callback 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.038: [egismoc] CMD_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.038: List callback 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.038: Number of currently enrolled fingerprints on the device is 0 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.038: [egismoc] LIST_STATES entering state 1 169s (process:3151): libfprint-device-DEBUG: 05:38:14.038: Device reported listing completion 169s (process:3151): libfprint-SSM-DEBUG: 05:38:14.038: [egismoc] LIST_STATES completed successfully 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.038: Task SSM done 169s (process:3151): libfprint-device-DEBUG: 05:38:14.038: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.039: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.039: Closing device 169s (process:3151): libfprint-egismoc-DEBUG: 05:38:14.039: Cancel 169s (process:3151): libfprint-device-DEBUG: 05:38:14.039: Device reported close completion 169s (process:3151): libfprint-device-DEBUG: 05:38:14.040: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:3151): libfprint-device-DEBUG: 05:38:14.040: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s listing - device should have prints 169s clear device storage 169s clear done 169s listing - device should be empty 169s enrolling 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 1, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 2, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 3, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 4, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 5, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 6, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 7, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 8, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 9, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 10, , None, None) 169s enroll done 169s listing - device should have 1 print 169s verifying 169s verify done 169s async identifying 169s indentification_done: 169s try to enroll duplicate 169s duplicate enroll attempt done 169s listing - device should still only have 1 print 169s enroll new finger 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 1, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 2, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 3, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 4, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 5, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 6, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 7, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 8, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 9, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x61e90928e080 (FpiDeviceEgisMoc at 0x41c85ed0)>, 10, , None, None) 169s enroll new finger done 169s listing - device should have 2 prints 169s deleting first print 169s delete done 169s listing - device should only have second print 169s clear device storage 169s clear done 169s listing - device should be empty 169s ** (umockdev-run:3147): DEBUG: 05:38:14.058: umockdev.vala:154: Removing test bed /tmp/umockdev.K1G012 169s (umockdev-run:3147): GLib-DEBUG: 05:38:14.067: unsetenv() is not thread-safe and should not be used after threads are created 169s PASS: libfprint-2/driver-egismoc-05a1.test 169s Running test: libfprint-2/driver-egismoc.test 169s ** (umockdev-run:3159): DEBUG: 05:38:14.122: umockdev.vala:127: Created udev test bed /tmp/umockdev.R2YB22 169s ** (umockdev-run:3159): DEBUG: 05:38:14.123: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 169s ** (umockdev-run:3159): DEBUG: 05:38:14.125: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 169s ** (umockdev-run:3159): DEBUG: 05:38:14.129: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.R2YB22/dev/bus/usb/003/012 169s ** (umockdev-run:3159): DEBUG: 05:38:14.129: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 169s ** (umockdev-run:3159): DEBUG: 05:38:14.130: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 169s ** (umockdev-run:3159): DEBUG: 05:38:14.134: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.R2YB22/dev/bus/usb/003/001 169s ** (umockdev-run:3159): DEBUG: 05:38:14.135: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 169s ** (umockdev-run:3159): DEBUG: 05:38:14.135: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 169s (process:3163): libfprint-context-DEBUG: 05:38:14.230: Initializing FpContext (libfprint version 1.94.9+tod1) 169s (process:3163): libfprint-tod-DEBUG: 05:38:14.231: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.233: 115072820: ../libfprint/drivers/egismoc/egismoc.c:1597 169s (process:3163): libfprint-context-DEBUG: 05:38:14.233: No driver found for USB device 1D6B:0002 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.233: egismoc_probe enter --> 169s (process:3163): libfprint-device-DEBUG: 05:38:14.235: Device reported probe completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.235: Completing action FPI_DEVICE_ACTION_PROBE in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.235: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.236: Opening device 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.237: [egismoc] DEV_INIT_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.238: [egismoc] DEV_INIT_STATES entering state 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.239: [egismoc] DEV_INIT_STATES entering state 2 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.243: [egismoc] DEV_INIT_STATES entering state 3 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.244: [egismoc] DEV_INIT_STATES entering state 4 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.245: [egismoc] DEV_INIT_STATES entering state 5 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.245: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.245: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.245: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.246: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.247: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.247: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.247: Firmware version callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.247: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.247: Device firmware version is 9050.1.1.81 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.247: [egismoc] DEV_INIT_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.247: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.247: Device reported open completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.247: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.247: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.248: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.248: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.248: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.248: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.248: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.249: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.250: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 3: FP1-20231016-3-5159A026-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 4: FP1-20231016-4-A25C1212-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Number of currently enrolled fingerprints on the device is 7 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.250: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.250: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.250: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.250: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.250: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.250: Clear storage 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.250: [egismoc] DELETE_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.251: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.251: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.251: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.252: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.253: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 3: FP1-20231016-3-5159A026-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 4: FP1-20231016-4-A25C1212-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Number of currently enrolled fingerprints on the device is 7 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.253: [egismoc] DELETE_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Get delete command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.253: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.253: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.254: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.255: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: Delete callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: Response prefix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.255: Device reported deletion completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.255: [egismoc] DELETE_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.255: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.255: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.255: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.255: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.255: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.256: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.257: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.257: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.257: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.257: Number of currently enrolled fingerprints on the device is 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.257: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.257: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.257: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.257: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.257: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.257: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3163): libfprint-device-DEBUG: 05:38:14.258: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.258: Enroll 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.258: [egismoc] ENROLL_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.258: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.258: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.258: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.259: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.260: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.260: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.260: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.260: Number of currently enrolled fingerprints on the device is 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.260: [egismoc] ENROLL_STATES entering state 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.260: [egismoc] ENROLL_STATES entering state 2 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.260: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.260: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.260: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.261: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.262: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.262: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.262: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.262: [egismoc] ENROLL_STATES entering state 3 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.262: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.262: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.262: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.267: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.269: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.269: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.269: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.269: [egismoc] ENROLL_STATES entering state 4 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.269: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.270: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.270: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.270: [egismoc] ENROLL_STATES entering state 5 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.270: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.270: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.270: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.271: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.272: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.272: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.272: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.272: [egismoc] ENROLL_STATES entering state 6 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.272: Get check command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.272: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.272: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.272: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.273: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.274: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.274: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.274: Enroll check callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.274: Response suffix valid: yes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.274: [egismoc] ENROLL_STATES entering state 7 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.274: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.274: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.274: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.274: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.275: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.275: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.275: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.275: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.275: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.275: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.276: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.277: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.278: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.278: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.278: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.278: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.278: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.278: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.278: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.279: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.280: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.280: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.280: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.280: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.280: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.281: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.281: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.281: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.281: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.281: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.281: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.282: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.283: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Partial capture successful. Please touch the sensor again (1/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.283: Device reported enroll progress, reported 1 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.283: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.283: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.283: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.284: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.285: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.285: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.285: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.285: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.285: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.285: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.285: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.286: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.287: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.287: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.287: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.287: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.287: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.288: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.288: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.288: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.288: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.288: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.288: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.289: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.290: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Partial capture successful. Please touch the sensor again (2/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.290: Device reported enroll progress, reported 2 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.290: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.290: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.290: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.291: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.292: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.292: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.292: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.292: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.292: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.292: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.292: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.293: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.294: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.294: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.294: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.294: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.294: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.294: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.295: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.295: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.295: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.295: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.295: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.295: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.296: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.297: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.297: Device reported enroll progress, reported 2 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.297: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.297: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.297: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.298: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.299: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.299: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.299: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.299: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.299: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.299: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.299: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.300: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.301: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.301: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.301: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.301: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.301: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.302: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.302: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.302: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.302: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.302: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.302: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.303: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.304: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.304: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.304: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.304: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.304: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.304: Partial capture successful. Please touch the sensor again (3/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.304: Device reported enroll progress, reported 3 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.305: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.305: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.305: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.305: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.305: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.307: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.307: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.307: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.307: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.307: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.307: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.307: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.308: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.308: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.308: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.308: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.308: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.309: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.309: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.309: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.309: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.309: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.309: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.309: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.309: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.310: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.311: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Partial capture successful. Please touch the sensor again (4/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.311: Device reported enroll progress, reported 4 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.311: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.311: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.311: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.312: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.313: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.313: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.313: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.313: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.313: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.313: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.313: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.314: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.315: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.315: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.315: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.315: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.315: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.315: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.315: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.316: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.316: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.316: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.316: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.316: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.316: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.317: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.317: Device reported enroll progress, reported 4 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.317: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.317: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.317: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.318: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.319: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.319: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.319: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.319: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.319: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.319: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.319: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.319: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.323: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.323: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.323: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.323: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.323: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.323: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.323: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.323: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.323: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.323: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.323: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.324: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.325: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Partial capture successful. Please touch the sensor again (5/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.325: Device reported enroll progress, reported 5 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.325: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.325: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.325: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.326: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.327: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.327: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.327: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.327: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.327: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.327: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.327: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.328: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.329: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.329: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.329: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.329: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.329: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.329: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.330: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.330: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.330: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.330: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.330: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.330: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.331: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.331: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.331: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.331: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.331: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.331: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.331: Partial capture successful. Please touch the sensor again (6/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.331: Device reported enroll progress, reported 6 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.331: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.331: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.332: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.332: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.332: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.333: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.333: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.333: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.333: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.333: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.333: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.333: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.334: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.335: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.335: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.335: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.335: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.335: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.336: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.336: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.336: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.336: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.336: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.336: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.336: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.337: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.337: Device reported enroll progress, reported 6 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.337: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.337: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.337: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.339: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.340: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.340: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.340: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.340: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.340: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.340: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.340: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.341: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.342: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.342: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.342: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.342: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.342: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.343: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.343: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.343: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.343: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.343: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.343: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.343: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.344: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.344: Device reported enroll progress, reported 6 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.344: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.344: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.344: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.345: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.346: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.346: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.346: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.346: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.346: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.346: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.346: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.347: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.347: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.347: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.347: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.347: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.347: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.347: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.348: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.348: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.348: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.348: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.348: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.348: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.349: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.350: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Partial capture successful. Please touch the sensor again (7/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.350: Device reported enroll progress, reported 7 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.350: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.350: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.350: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.351: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.351: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.351: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.351: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.351: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.351: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.351: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.351: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.352: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.353: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.353: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.353: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.353: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.353: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.353: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.354: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.354: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.354: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.354: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.354: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.354: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.354: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.355: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.355: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.355: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.355: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.355: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.355: Partial capture successful. Please touch the sensor again (8/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.355: Device reported enroll progress, reported 8 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.355: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.356: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.356: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.356: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.356: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.357: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.357: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.357: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.357: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.357: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.357: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.357: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.358: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.359: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.359: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.359: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.359: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.359: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.359: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.360: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.360: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.360: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.360: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.360: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.360: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-device-DEBUG: 05:38:14.360: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.360: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.361: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Partial capture successful. Please touch the sensor again (9/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.361: Device reported enroll progress, reported 9 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.361: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.361: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.361: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.362: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.363: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.363: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.363: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.363: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.363: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.363: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.363: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.364: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.365: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.365: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.365: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.365: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.365: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.366: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.366: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.366: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.366: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.366: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.366: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.367: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.367: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.367: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.367: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.367: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.367: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.367: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.367: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.367: Device reported enroll progress, reported 9 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.368: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.368: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.368: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.368: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.368: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.369: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.369: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.369: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.369: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.369: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.369: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.369: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.370: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.371: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.371: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.371: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.371: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.371: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.372: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.372: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.372: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.372: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.372: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.372: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.372: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.373: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.373: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.373: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.373: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.373: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.373: Partial capture successful. Please touch the sensor again (10/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.373: Device reported enroll progress, reported 10 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.373: [egismoc] ENROLL_STATES entering state 12 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.373: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.374: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.374: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.374: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.375: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.375: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.375: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.375: [egismoc] ENROLL_STATES entering state 13 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.375: New fingerprint ID: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.375: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.375: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.375: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.376: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.377: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.377: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.377: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.377: [egismoc] ENROLL_STATES entering state 14 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.377: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.377: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.377: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.377: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.378: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.378: [egismoc] ENROLL_STATES entering state 15 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: Enrollment was successful! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.378: Device reported enroll completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.378: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3163): libfprint-device-DEBUG: 05:38:14.378: Print for finger FP_FINGER_LEFT_INDEX enrolled 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.378: [egismoc] ENROLL_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.378: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.378: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.378: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.378: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.378: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.379: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.380: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.380: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.380: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.380: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.380: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-device-DEBUG: 05:38:14.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Identify or Verify 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.380: [egismoc] IDENTIFY_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.380: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.380: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.381: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.382: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.382: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.382: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.382: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.382: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.382: [egismoc] IDENTIFY_STATES entering state 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.382: [egismoc] IDENTIFY_STATES entering state 2 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.382: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.382: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.382: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.383: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.384: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.384: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.384: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.384: [egismoc] IDENTIFY_STATES entering state 3 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.384: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.384: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.384: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.384: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.385: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.385: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.385: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.385: [egismoc] IDENTIFY_STATES entering state 4 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.385: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.386: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.386: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.386: [egismoc] IDENTIFY_STATES entering state 5 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.386: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.386: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.386: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.387: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.387: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.387: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.387: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.387: [egismoc] IDENTIFY_STATES entering state 6 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.387: Get check command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.387: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.387: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.387: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.388: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.389: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Identify check callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Identify successful for: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Verifying against: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-device-DEBUG: 05:38:14.389: Device reported verify result 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.389: [egismoc] IDENTIFY_STATES entering state 7 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.389: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.389: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.390: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.390: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.390: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.390: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.390: [egismoc] IDENTIFY_STATES entering state 8 169s (process:3163): libfprint-device-DEBUG: 05:38:14.390: Device reported verify completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.390: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.390: [egismoc] IDENTIFY_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.390: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.390: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.391: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-device-DEBUG: 05:38:14.391: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.391: Identify or Verify 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.391: [egismoc] IDENTIFY_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.391: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.392: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.392: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.392: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.393: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.393: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.393: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.393: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.393: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.393: [egismoc] IDENTIFY_STATES entering state 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.393: [egismoc] IDENTIFY_STATES entering state 2 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.393: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.393: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.393: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.394: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.395: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.395: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.395: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.395: [egismoc] IDENTIFY_STATES entering state 3 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.395: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.395: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.395: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.396: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.396: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.396: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.396: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.396: [egismoc] IDENTIFY_STATES entering state 4 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.396: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.397: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.397: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.397: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.397: [egismoc] IDENTIFY_STATES entering state 5 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.397: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.397: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.397: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.398: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.399: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.399: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.399: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.399: [egismoc] IDENTIFY_STATES entering state 6 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.399: Get check command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.399: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.399: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.399: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.399: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.400: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.400: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.400: Identify check callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.400: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.400: Identify successful for: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-device-DEBUG: 05:38:14.401: Device reported identify result 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.401: [egismoc] IDENTIFY_STATES entering state 7 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.401: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.401: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.401: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.401: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.402: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.402: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.402: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.402: [egismoc] IDENTIFY_STATES entering state 8 169s (process:3163): libfprint-device-DEBUG: 05:38:14.402: Device reported identify completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.402: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.402: [egismoc] IDENTIFY_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.402: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.402: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.402: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-device-DEBUG: 05:38:14.403: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.403: Enroll 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.403: [egismoc] ENROLL_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.404: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.404: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.404: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.404: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.405: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.405: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.405: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.405: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.405: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.405: [egismoc] ENROLL_STATES entering state 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.405: [egismoc] ENROLL_STATES entering state 2 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.405: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.405: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.405: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.406: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.406: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.406: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.406: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.406: [egismoc] ENROLL_STATES entering state 3 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.407: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.407: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.407: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.407: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.408: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.408: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.408: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.408: [egismoc] ENROLL_STATES entering state 4 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.408: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.408: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.409: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.409: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.409: [egismoc] ENROLL_STATES entering state 5 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.409: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.409: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.409: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.410: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.411: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.411: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.411: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.411: [egismoc] ENROLL_STATES entering state 6 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.411: Get check command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.411: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.411: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.411: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.412: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.412: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.412: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.413: Enroll check callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.413: Response suffix valid: NO 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.413: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.413: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.413: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.413: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 169s (process:3163): libfprint-device-DEBUG: 05:38:14.413: Device reported enroll completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.413: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3163): libfprint-device-DEBUG: 05:38:14.413: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.413: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.413: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.413: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.413: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.413: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.413: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.414: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.415: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.415: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.415: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.415: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.415: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.415: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-device-DEBUG: 05:38:14.415: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Enroll 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.415: [egismoc] ENROLL_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.415: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.415: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.416: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.417: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.417: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.417: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.417: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.417: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.417: [egismoc] ENROLL_STATES entering state 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.417: [egismoc] ENROLL_STATES entering state 2 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.417: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.417: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.417: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.417: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.418: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.418: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.418: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.418: [egismoc] ENROLL_STATES entering state 3 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.418: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.418: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.418: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.419: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.420: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.420: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.420: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.420: [egismoc] ENROLL_STATES entering state 4 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.420: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.420: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.421: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.421: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.421: [egismoc] ENROLL_STATES entering state 5 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.421: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.421: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.421: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.422: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.423: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.423: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.423: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.423: [egismoc] ENROLL_STATES entering state 6 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.423: Get check command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.423: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.423: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.423: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.424: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.425: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.425: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.425: Enroll check callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.425: Response suffix valid: yes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.425: [egismoc] ENROLL_STATES entering state 7 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.425: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.425: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.425: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.425: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.426: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.426: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.426: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.426: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.426: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.426: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.426: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.429: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.430: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.430: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.430: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.430: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.430: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.430: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.430: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.431: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.431: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.431: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.431: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.431: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.431: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.431: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.432: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.432: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.432: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.432: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.432: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.432: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.433: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.434: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Partial capture successful. Please touch the sensor again (1/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.434: Device reported enroll progress, reported 1 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.434: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.434: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.434: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.435: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.436: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.436: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.436: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.436: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.436: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.436: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.436: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.437: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.438: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.438: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.438: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.438: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.438: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.438: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.438: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.438: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.438: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.439: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.439: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.439: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.440: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.440: Device reported enroll progress, reported 1 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.440: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.440: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.440: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.441: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.442: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.442: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.442: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.442: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.442: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.442: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.442: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.443: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.444: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.444: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.444: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.444: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.444: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.444: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.445: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.445: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.445: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.445: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.445: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.445: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.445: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.446: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Partial capture successful. Please touch the sensor again (2/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.446: Device reported enroll progress, reported 2 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.446: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.446: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.446: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.447: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.448: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.448: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.448: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.448: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.448: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.448: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.448: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.448: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.449: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.449: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.449: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.449: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.449: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.450: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.450: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.450: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.450: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.450: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.450: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.451: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.451: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.451: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.451: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.451: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.451: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.451: Partial capture successful. Please touch the sensor again (3/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.451: Device reported enroll progress, reported 3 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.452: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.452: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.452: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.452: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.452: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.453: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.453: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.453: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.453: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.453: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.453: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.453: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.454: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.454: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.454: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.454: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.454: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.454: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.455: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.455: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.455: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.455: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.455: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.455: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.456: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.457: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.457: Device reported enroll progress, reported 3 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.457: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.457: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.457: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.458: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.458: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.458: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.459: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.459: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.459: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.459: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.459: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.459: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.460: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.460: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.460: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.460: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.460: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.460: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.461: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.461: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.461: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.461: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.461: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.461: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.462: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.463: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.463: Device reported enroll progress, reported 3 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.463: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.463: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.463: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.464: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.465: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.465: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.465: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.465: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.465: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.465: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.465: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.465: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.466: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.466: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.466: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.466: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.466: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.466: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.467: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.467: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.467: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.467: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.467: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.467: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.468: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.468: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Partial capture successful. Please touch the sensor again (4/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.468: Device reported enroll progress, reported 4 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.468: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.468: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.468: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.469: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.470: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.470: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.470: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.470: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.470: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.470: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.470: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.470: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.471: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.471: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.471: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.471: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.471: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.471: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.472: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.472: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.472: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.472: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.472: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.472: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.473: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.473: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Partial capture successful. Please touch the sensor again (5/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.473: Device reported enroll progress, reported 5 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.473: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.473: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.473: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.474: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.475: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.475: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.475: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.475: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.475: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.475: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.475: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.475: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.476: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.476: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.476: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.476: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.476: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.477: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.477: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.477: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.477: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.477: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.477: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.477: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.478: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Partial capture successful. Please touch the sensor again (6/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.478: Device reported enroll progress, reported 6 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.478: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.478: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.478: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.479: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.479: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.479: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.479: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.479: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.479: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.479: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.479: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.480: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.481: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.481: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.481: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.481: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.481: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.481: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.481: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.481: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.481: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.481: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.481: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.481: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.482: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.483: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Partial capture successful. Please touch the sensor again (7/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.483: Device reported enroll progress, reported 7 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.483: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.483: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.483: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.483: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.484: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.484: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.484: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.484: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.484: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.484: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.484: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.485: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.486: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.486: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.486: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.486: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.486: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.486: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.486: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.487: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.487: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.487: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.487: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.487: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.487: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.488: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Partial capture successful. Please touch the sensor again (8/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.488: Device reported enroll progress, reported 8 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.488: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.488: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.488: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.489: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.490: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.490: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.490: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.490: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.490: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.490: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.490: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.490: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.491: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.491: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.491: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.491: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.491: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.491: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.491: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.491: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.491: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.491: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.491: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.491: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.492: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.493: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Partial capture successful. Please touch the sensor again (9/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.493: Device reported enroll progress, reported 9 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.493: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.493: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.493: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.493: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.494: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.494: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.494: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.494: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.494: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.494: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.494: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.495: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.495: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.495: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.495: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.495: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.495: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.495: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.496: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.496: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.496: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.496: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.496: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.496: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.497: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.497: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.497: Device reported enroll progress, reported 9 of 10 have been completed 169s listing - device should have prints 169s clear device storage 169s clear done 169s listing - device should be empty 169s enrolling 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 1, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 2, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 3, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 4, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 5, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 6, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 7, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 8, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 9, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 10, , None, None) 169s enroll done 169s listing - device should have 1 print 169s verifying 169s verify done 169s async identifying 169s indentification_done: 169s try to enroll duplicate 169s duplicate enroll attempt done 169s listing - device should still only have 1 print 169s enroll new finger 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 1, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 2, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 3, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 4, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 5, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 6, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 7, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 8, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 9, , None, None) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:3163): libfprint-SSM-DEBUG: 05:38:14.497: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.497: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.497: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.498: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.499: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.499: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.499: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.499: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.499: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.499: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.499: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.499: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.500: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.500: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.500: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.500: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.500: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.500: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.500: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.500: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.500: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.500: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.501: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.501: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.502: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.502: Device reported enroll progress, reported 9 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.502: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.502: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.502: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.503: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.503: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.503: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.503: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.503: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.503: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.503: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.503: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.504: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.505: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.505: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.505: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.505: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.505: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.505: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.505: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.505: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.505: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.505: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.505: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.506: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.507: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Response suffix valid: NO 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Response suffix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.507: Device reported enroll progress, reported 9 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.507: [egismoc] ENROLL_STATES entering state 8 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.507: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.507: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.507: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.508: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.508: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.509: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.509: [egismoc] ENROLL_STATES entering state 9 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.509: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.509: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.509: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.509: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.510: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.510: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.510: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.510: [egismoc] ENROLL_STATES entering state 10 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.510: Wait for finger on sensor 169s (process:3163): libfprint-device-DEBUG: 05:38:14.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.511: Finger on sensor callback 169s (process:3163): libfprint-device-DEBUG: 05:38:14.511: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.511: [egismoc] ENROLL_STATES entering state 11 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.511: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.511: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.511: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.512: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.512: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Read capture callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Response prefix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Response suffix valid: yes 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Partial capture successful. Please touch the sensor again (10/10) 169s (process:3163): libfprint-device-DEBUG: 05:38:14.512: Device reported enroll progress, reported 10 of 10 have been completed 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.512: [egismoc] ENROLL_STATES entering state 12 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.512: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.512: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.513: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.514: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.514: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.514: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.514: [egismoc] ENROLL_STATES entering state 13 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.514: New fingerprint ID: FP1-00000000-7-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.514: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.514: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.514: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.515: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.516: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.516: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.516: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.516: [egismoc] ENROLL_STATES entering state 14 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.516: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.516: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.516: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.517: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.518: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: Task SSM next state callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.518: [egismoc] ENROLL_STATES entering state 15 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: Enrollment was successful! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.518: Device reported enroll completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.518: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3163): libfprint-device-DEBUG: 05:38:14.518: Print for finger FP_FINGER_RIGHT_INDEX enrolled 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.518: [egismoc] ENROLL_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.518: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.518: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.518: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.518: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.518: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.519: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.520: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Device fingerprint 2: FP1-00000000-7-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Number of currently enrolled fingerprints on the device is 2 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.520: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.520: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.520: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.520: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.520: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Delete 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.520: [egismoc] DELETE_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.520: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.520: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.521: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.522: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Device fingerprint 1: FP1-00000000-2-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Device fingerprint 2: FP1-00000000-7-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Number of currently enrolled fingerprints on the device is 2 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.522: [egismoc] DELETE_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Get delete command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.522: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.522: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.523: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.523: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: Delete callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: Response prefix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.523: Device reported deletion completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.523: [egismoc] DELETE_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.523: Completing action FPI_DEVICE_ACTION_DELETE in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.523: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.523: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.523: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.523: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.524: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.525: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Device fingerprint 1: FP1-00000000-7-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.525: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.525: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.525: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.525: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.525: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Clear storage 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.525: [egismoc] DELETE_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.525: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.525: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.526: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.527: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: Device fingerprint 1: FP1-00000000-7-00000000-nobody 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: Number of currently enrolled fingerprints on the device is 1 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.527: [egismoc] DELETE_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: Get delete command 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.527: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.527: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.527: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.528: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: Delete callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: Response prefix valid: yes 169s (process:3163): libfprint-device-DEBUG: 05:38:14.528: Device reported deletion completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.528: [egismoc] DELETE_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.528: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.528: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: List 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.528: [egismoc] LIST_STATES entering state 0 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: Execute command and get response 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.528: Get check bytes 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.528: [egismoc] CMD_STATES entering state 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.529: [egismoc] CMD_STATES entering state 1 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.530: Command receive callback 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.530: [egismoc] CMD_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.530: List callback 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.530: Number of currently enrolled fingerprints on the device is 0 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.530: [egismoc] LIST_STATES entering state 1 169s (process:3163): libfprint-device-DEBUG: 05:38:14.530: Device reported listing completion 169s (process:3163): libfprint-SSM-DEBUG: 05:38:14.530: [egismoc] LIST_STATES completed successfully 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.530: Task SSM done 169s (process:3163): libfprint-device-DEBUG: 05:38:14.530: Completing action FPI_DEVICE_ACTION_LIST in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.530: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.530: Closing device 169s (process:3163): libfprint-egismoc-DEBUG: 05:38:14.530: Cancel 169s (process:3163): libfprint-device-DEBUG: 05:38:14.530: Device reported close completion 169s (process:3163): libfprint-device-DEBUG: 05:38:14.531: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:3163): libfprint-device-DEBUG: 05:38:14.531: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 169s finger status: 169s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7959e088e080 (FpiDeviceEgisMoc at 0x234f6370)>, 10, , None, None) 169s enroll new finger done 169s listing - device should have 2 prints 169s deleting first print 169s delete done 169s listing - device should only have second print 169s clear device storage 169s clear done 169s listing - device should be empty 169s ** (umockdev-run:3159): DEBUG: 05:38:14.548: umockdev.vala:154: Removing test bed /tmp/umockdev.R2YB22 169s (umockdev-run:3159): GLib-DEBUG: 05:38:14.556: unsetenv() is not thread-safe and should not be used after threads are created 169s PASS: libfprint-2/driver-egismoc.test 169s Running test: libfprint-2/driver-vfs0050.test 169s ** (umockdev-run:3171): DEBUG: 05:38:14.609: umockdev.vala:127: Created udev test bed /tmp/umockdev.F3WZ12 169s ** (umockdev-run:3171): DEBUG: 05:38:14.609: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 169s ** (umockdev-run:3171): DEBUG: 05:38:14.611: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 169s ** (umockdev-run:3171): DEBUG: 05:38:14.615: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.F3WZ12/dev/bus/usb/001/004 169s ** (umockdev-run:3171): DEBUG: 05:38:14.615: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 169s ** (umockdev-run:3171): DEBUG: 05:38:14.616: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 169s ** (umockdev-run:3171): DEBUG: 05:38:14.620: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.F3WZ12/dev/bus/usb/001/001 169s ** (umockdev-run:3171): DEBUG: 05:38:14.620: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 169s ** (umockdev-run:3171): DEBUG: 05:38:14.621: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 169s (umockdev-run:3171): GLib-GIO-DEBUG: 05:38:14.623: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 169s (process:3175): libfprint-context-DEBUG: 05:38:14.746: Initializing FpContext (libfprint version 1.94.9+tod1) 169s (process:3175): libfprint-tod-DEBUG: 05:38:14.746: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 169s (process:3175): libfprint-context-DEBUG: 05:38:14.749: No driver found for USB device 1D6B:0002 169s (process:3175): libfprint-device-DEBUG: 05:38:14.749: Device reported probe completion 169s (process:3175): libfprint-device-DEBUG: 05:38:14.749: Completing action FPI_DEVICE_ACTION_PROBE in idle! 169s (process:3175): libfprint-device-DEBUG: 05:38:14.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.751: [vfs0050] SSM_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.752: [vfs0050] SSM_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.753: [vfs0050] SSM_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.753: [vfs0050] SSM_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.753: [vfs0050] SUBSM1_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.754: [vfs0050] SUBSM1_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.755: [vfs0050] SUBSM1_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.756: [vfs0050] SUBSM1_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.756: [vfs0050] SSM_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.756: [vfs0050] SUBSM2_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.756: [vfs0050] SUBSM2_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.757: [vfs0050] SUBSM2_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.758: [vfs0050] SUBSM2_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.759: [vfs0050] SUBSM2_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.760: [vfs0050] SUBSM2_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.760: [vfs0050] SUBSM2_STATES entering state 6 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.760: [vfs0050] SUBSM1_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.761: [vfs0050] SUBSM1_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.762: [vfs0050] SUBSM1_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.763: [vfs0050] SUBSM1_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.763: [vfs0050] SUBSM2_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.763: [vfs0050] SSM_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.763: [vfs0050] SSM_STATES completed successfully 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.763: Image device open completed 169s (process:3175): libfprint-device-DEBUG: 05:38:14.763: Device reported open completion 169s (process:3175): libfprint-device-DEBUG: 05:38:14.763: Completing action FPI_DEVICE_ACTION_OPEN in idle! 169s (process:3175): libfprint-device-DEBUG: 05:38:14.763: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3175): libfprint-device-DEBUG: 05:38:14.764: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.764: Activating image device 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.764: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.764: [vfs0050] SSM_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.765: [vfs0050] SSM_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.766: [vfs0050] SSM_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.767: [vfs0050] SSM_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.767: [vfs0050] SUBSM1_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.767: [vfs0050] SUBSM1_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.768: [vfs0050] SUBSM1_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.769: [vfs0050] SUBSM1_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.769: [vfs0050] SSM_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.769: [vfs0050] SUBSM2_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.770: [vfs0050] SUBSM2_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.770: [vfs0050] SUBSM2_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.771: [vfs0050] SUBSM2_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.772: [vfs0050] SUBSM2_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.773: [vfs0050] SUBSM2_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.773: [vfs0050] SUBSM2_STATES entering state 6 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.773: [vfs0050] SUBSM1_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.774: [vfs0050] SUBSM1_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.775: [vfs0050] SUBSM1_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.776: [vfs0050] SUBSM1_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.776: [vfs0050] SUBSM2_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.776: [vfs0050] SSM_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.776: [vfs0050] SUBSM2_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.776: [vfs0050] SUBSM2_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.777: [vfs0050] SUBSM2_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.778: [vfs0050] SUBSM2_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.779: [vfs0050] SUBSM2_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.780: [vfs0050] SUBSM2_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.781: [vfs0050] SUBSM2_STATES entering state 6 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.781: [vfs0050] SUBSM2_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.781: [vfs0050] SSM_STATES entering state 6 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.781: Image device activation completed 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.781: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.781: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 169s (process:3175): libfprint-device-DEBUG: 05:38:14.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.781: [vfs0050] SSM_STATES entering state 7 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.782: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-device-DEBUG: 05:38:14.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.782: Image device reported finger status: on 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.782: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.783: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.784: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.787: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.788: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.789: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.790: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.791: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.792: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.793: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.794: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.795: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.796: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.797: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.798: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.799: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.800: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.800: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.801: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.802: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.803: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.804: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.805: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.806: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.806: [vfs0050] SSM_STATES entering state 8 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.807: [vfs0050] SSM_STATES entering state 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.807: 1740202694807976 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.807: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 91 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 85 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.808: 85 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 48 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 48 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.809: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.810: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 91 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.811: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.812: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.813: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.814: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.815: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.816: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.817: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.818: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 74 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.819: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.820: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.821: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.821: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.821: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.821: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.821: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.821: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 76 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 74 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.822: 48 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 76 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.823: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 85 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 74 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 48 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 85 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 80 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 74 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 72 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 91 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.824: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 91 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 76 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 72 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 80 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 76 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 74 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 74 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.825: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 100 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 3 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 2 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.826: 1 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: offsets_filtered: 1740202694828483 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 5 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.828: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.829: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.830: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.831: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 99 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 98 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 97 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 96 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 95 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 93 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 91 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 88 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 86 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 85 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.832: 85 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 84 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 79 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 75 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 48 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.833: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 30 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.834: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 19 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.835: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 18 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 16 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 11 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 12 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.836: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 64 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 48 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 94 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 92 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 90 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 89 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 87 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 83 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 81 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 77 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 70 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 20 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 24 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.837: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 60 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 54 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 43 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 42 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 36 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 47 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 46 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 32 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 26 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 23 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 25 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 62 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 56 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 49 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 44 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 37 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 38 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.838: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 52 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 73 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 71 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 69 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 68 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 67 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 66 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 61 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 59 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 57 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 51 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 33 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 34 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 65 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 63 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 58 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 55 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 50 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 53 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 45 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 41 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 40 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 39 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 35 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 31 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 29 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 28 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 27 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 22 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 21 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 17 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 15 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 14 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 13 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 10 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 9 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 8 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 7 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 4 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 6 169s (process:3175): libfprint-assembling-DEBUG: 05:38:14.839: 1 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.840: Image device captured an image 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 169s (process:3175): libfprint-device-DEBUG: 05:38:14.841: Device reported finger status change: FP_FINGER_STATUS_PRESENT 169s (process:3175): libfprint-device-DEBUG: 05:38:14.841: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.841: Image device reported finger status: off 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.841: Deactivating image device 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.841: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 169s (process:3175): libfprint-device-DEBUG: 05:38:14.868: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 169s (process:3175): libfprint-image-DEBUG: 05:38:14.884: Minutiae scan completed in 0.042782 secs 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.907: [vfs0050] SSM_STATES entering state 10 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.907: [vfs0050] SSM_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.907: [vfs0050] SUBSM1_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.908: [vfs0050] SUBSM1_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.909: [vfs0050] SUBSM1_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.909: [vfs0050] SUBSM1_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.909: [vfs0050] SSM_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.909: [vfs0050] SUBSM2_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.910: [vfs0050] SUBSM2_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.910: [vfs0050] SUBSM2_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.911: [vfs0050] SUBSM2_STATES entering state 3 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.912: [vfs0050] SUBSM2_STATES entering state 4 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.912: [vfs0050] SUBSM2_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.913: [vfs0050] SUBSM2_STATES entering state 6 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.913: [vfs0050] SUBSM1_STATES entering state 0 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.913: [vfs0050] SUBSM1_STATES entering state 1 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.914: [vfs0050] SUBSM1_STATES entering state 2 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.915: [vfs0050] SUBSM1_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.915: [vfs0050] SUBSM2_STATES completed successfully 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.915: [vfs0050] SSM_STATES entering state 5 169s (process:3175): libfprint-SSM-DEBUG: 05:38:14.915: [vfs0050] SSM_STATES completed successfully 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.915: Image device deactivation completed 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.915: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 169s (process:3175): libfprint-device-DEBUG: 05:38:14.915: Device reported capture completion 169s (process:3175): libfprint-device-DEBUG: 05:38:14.915: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 169s (process:3175): libfprint-device-DEBUG: 05:38:14.915: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:3175): libfprint-image_device-DEBUG: 05:38:14.915: Image device close completed 169s (process:3175): libfprint-device-DEBUG: 05:38:14.915: Device reported close completion 169s (process:3175): libfprint-device-DEBUG: 05:38:14.915: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:3175): libfprint-device-DEBUG: 05:38:14.915: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ** (umockdev-run:3171): DEBUG: 05:38:15.179: umockdev.vala:154: Removing test bed /tmp/umockdev.F3WZ12 170s (umockdev-run:3171): GLib-DEBUG: 05:38:15.187: unsetenv() is not thread-safe and should not be used after threads are created 170s Comparing PNGs /tmp/libfprint-umockdev-test-hdw1xsfz/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 170s PASS: libfprint-2/driver-vfs0050.test 170s Running test: libfprint-2/driver-elan-cobo.test 170s ** (umockdev-run:3184): DEBUG: 05:38:15.311: umockdev.vala:127: Created udev test bed /tmp/umockdev.XJ5I22 170s ** (umockdev-run:3184): DEBUG: 05:38:15.311: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 170s ** (umockdev-run:3184): DEBUG: 05:38:15.313: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 170s ** (umockdev-run:3184): DEBUG: 05:38:15.316: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.XJ5I22/dev/bus/usb/001/045 170s ** (umockdev-run:3184): DEBUG: 05:38:15.316: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 170s ** (umockdev-run:3184): DEBUG: 05:38:15.317: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 170s ** (umockdev-run:3184): DEBUG: 05:38:15.320: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.XJ5I22/dev/bus/usb/001/001 170s ** (umockdev-run:3184): DEBUG: 05:38:15.320: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 170s ** (umockdev-run:3184): DEBUG: 05:38:15.320: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 170s (process:3188): libfprint-context-DEBUG: 05:38:15.432: Initializing FpContext (libfprint version 1.94.9+tod1) 170s (process:3188): libfprint-tod-DEBUG: 05:38:15.432: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 170s (process:3188): libfprint-context-DEBUG: 05:38:15.435: No driver found for USB device 1D6B:0002 170s (process:3188): libfprint-device-DEBUG: 05:38:15.435: Device reported probe completion 170s (process:3188): libfprint-device-DEBUG: 05:38:15.435: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s (process:3188): libfprint-device-DEBUG: 05:38:15.435: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.439: 116279340: ../libfprint/drivers/elan.c:908 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.440: Image device open completed 170s (process:3188): libfprint-device-DEBUG: 05:38:15.440: Device reported open completion 170s (process:3188): libfprint-device-DEBUG: 05:38:15.440: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s (process:3188): libfprint-device-DEBUG: 05:38:15.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s (process:3188): libfprint-device-DEBUG: 05:38:15.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.440: Activating image device 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.440: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.440: 116280179: ../libfprint/drivers/elan.c:960 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.440: 116280185: ../libfprint/drivers/elan.c:951 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.440: 116280190: ../libfprint/drivers/elan.c:892 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.440: 116280194: ../libfprint/drivers/elan.c:100 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.440: [elan] ACTIVATE_NUM_STATES entering state 0 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.440: 116280213: ../libfprint/drivers/elan.c:820 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.441: 116280939: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.441: 116280948: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.441: 116280953: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.442: 116281758: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.442: 116281769: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.442: [elan] ACTIVATE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.442: 116281781: ../libfprint/drivers/elan.c:820 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.442: FW ver 0x0140 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.442: [elan] ACTIVATE_NUM_STATES entering state 2 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.442: 116281800: ../libfprint/drivers/elan.c:820 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116282547: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116282556: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116282561: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283302: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283311: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.443: [elan] ACTIVATE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283322: ../libfprint/drivers/elan.c:820 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: sensor dimensions, WxH: 144x64 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.443: [elan] ACTIVATE_NUM_STATES entering state 4 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283337: ../libfprint/drivers/elan.c:820 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283348: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.443: [elan] ACTIVATE_NUM_STATES completed successfully 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283359: ../libfprint/drivers/elan.c:881 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.443: Image device activation completed 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.443: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283380: ../libfprint/drivers/elan.c:960 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.443: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283393: ../libfprint/drivers/elan.c:960 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283398: ../libfprint/drivers/elan.c:792 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283402: ../libfprint/drivers/elan.c:100 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.443: [elan] CALIBRATE_NUM_STATES entering state 0 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.443: 116283412: ../libfprint/drivers/elan.c:691 170s (process:3188): libfprint-device-DEBUG: 05:38:15.444: Device reported finger status change: FP_FINGER_STATUS_NEEDED 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.447: 116286763: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.447: 116286781: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.447: 116286786: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116287497: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116287510: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.448: [elan] CALIBRATE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116287521: ../libfprint/drivers/elan.c:691 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116287525: ../libfprint/drivers/elan.c:156 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116287553: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.448: [elan] CALIBRATE_NUM_STATES entering state 2 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116287569: ../libfprint/drivers/elan.c:691 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116288256: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116288270: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.448: 116288275: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289026: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289036: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.449: [elan] CALIBRATE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289046: ../libfprint/drivers/elan.c:691 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289051: ../libfprint/drivers/elan.c:634 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: calibration mean: 8248, bg mean: 7978, delta: 270 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.449: [elan] CALIBRATE_NUM_STATES completed successfully 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289075: ../libfprint/drivers/elan.c:776 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289080: ../libfprint/drivers/elan.c:620 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.449: 116289084: ../libfprint/drivers/elan.c:100 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.449: [elan] CAPTURE_NUM_STATES entering state 0 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.450: 116289786: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.450: 116289795: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.450: 116289800: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.450: skipping read, not expecting anything 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.450: 116289809: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.450: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.451: 116290560: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.451: 116290570: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.451: 116290575: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.451: 116291384: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.451: 116291394: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.451: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-device-DEBUG: 05:38:15.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.451: Image device reported finger status: on 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.451: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.451: 116291462: ../libfprint/drivers/elan.c:960 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.452: 116292263: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.452: 116292293: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.452: 116292323: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.453: 116293223: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.453: 116293235: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.453: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.453: 116293246: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.453: 116293251: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.453: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.454: 116294064: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.454: 116294073: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.454: 116294078: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.455: 116294846: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.455: 116294856: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.455: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.455: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.456: 116295660: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.456: 116295670: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.456: 116295674: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116296540: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116296563: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.457: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116296572: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116296577: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.457: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116297415: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116297425: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.457: 116297430: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.458: 116298365: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.458: 116298374: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.458: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.458: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.459: 116299189: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.459: 116299198: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.459: 116299203: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.460: 116300167: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.460: 116300190: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.460: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.460: 116300207: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.460: 116300214: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.460: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.461: 116300967: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.461: 116300980: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.461: 116300990: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.462: 116301932: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.462: 116301941: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.462: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.462: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.463: 116302650: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.463: 116302659: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.463: 116302663: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116303520: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116303533: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.464: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116303543: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116303548: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.464: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116304214: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116304230: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.464: 116304234: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.465: 116304962: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.465: 116304970: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.465: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.465: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116305656: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116305665: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116305670: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116306381: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116306394: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.466: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116306405: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.466: 116306455: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.466: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.467: 116307142: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.467: 116307155: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.467: 116307162: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.468: 116307875: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.468: 116307884: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.468: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.468: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116308530: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116308547: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116308552: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116309241: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116309254: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.469: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116309265: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.469: 116309270: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.469: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.470: 116310023: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.470: 116310032: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.470: 116310037: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.471: 116310959: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.471: 116310968: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.471: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.471: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116311735: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116311744: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116311749: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116312413: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116312431: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.472: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116312441: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.472: 116312446: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.472: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.473: 116313146: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.473: 116313155: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.473: 116313160: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.474: 116313916: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.474: 116313925: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.474: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.474: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116314615: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116314624: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116314629: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116315344: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116315357: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.475: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116315368: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.475: 116315373: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.475: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.476: 116316113: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.476: 116316134: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.476: 116316143: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.477: 116316858: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.477: 116316867: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.477: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.477: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.478: 116317617: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.478: 116317631: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.478: 116317639: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.478: 116318459: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.479: 116318475: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.479: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.479: 116318493: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.479: 116318525: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.479: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.479: 116319264: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.479: 116319275: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.479: 116319281: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.480: 116319996: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.480: 116320037: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.480: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.480: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.481: 116320779: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.481: 116320790: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.481: 116320795: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116321540: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116321554: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.482: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116321567: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116321573: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.482: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116322326: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116322336: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.482: 116322343: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.483: 116323111: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.483: 116323121: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.483: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.483: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.484: 116323784: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.484: 116323793: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.484: 116323797: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116324573: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116324600: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.485: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116324617: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116324622: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.485: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116325343: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116325351: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.485: 116325356: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.486: 116326046: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.486: 116326056: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.486: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.486: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.487: 116326767: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.487: 116326780: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.487: 116326787: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116327504: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116327521: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.488: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116327540: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116327549: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.488: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116328322: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116328341: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.488: 116328347: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.489: 116329046: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.489: 116329055: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.489: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.489: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.490: 116329766: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.490: 116329775: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.490: 116329779: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116330666: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116330683: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.491: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116330700: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116330733: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.491: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116331399: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116331408: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.491: 116331413: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.492: 116332321: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.492: 116332336: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.492: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.492: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.493: 116333158: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.493: 116333167: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.493: 116333172: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.494: 116333978: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.494: 116333998: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.494: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.494: 116334019: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.494: 116334056: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.494: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.495: 116334902: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.495: 116334919: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.495: 116334931: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.496: 116335689: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.496: 116335698: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.496: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.496: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.496: 116336412: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.496: 116336432: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.496: 116336436: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.497: 116337410: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.497: 116337423: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.497: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.497: 116337433: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.497: 116337437: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.497: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.498: 116338138: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.498: 116338148: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.498: 116338152: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.499: 116338908: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.499: 116338917: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.499: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-image_device-DEBUG: 05:38:15.499: Image device reported finger status: on 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.500: 116339810: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.500: 116339820: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.500: 116339824: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.501: 116340854: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.501: 116340877: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.501: [elan] CAPTURE_NUM_STATES entering state 3 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.501: 116340888: ../libfprint/drivers/elan.c:203 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.501: 116340893: ../libfprint/drivers/elan.c:118 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.501: [elan] CAPTURE_NUM_STATES entering state 1 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.502: 116341697: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.502: 116341707: ../libfprint/drivers/elan.c:366 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.502: 116341712: ../libfprint/drivers/elan.c:379 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.503: 116342552: ../libfprint/drivers/elan.c:346 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.503: 116342567: ../libfprint/drivers/elan.c:335 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.503: [elan] CAPTURE_NUM_STATES entering state 2 170s (process:3188): libfprint-SSM-DEBUG: 05:38:15.503: [elan] CAPTURE_NUM_STATES completed successfully 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.503: 116342610: ../libfprint/drivers/elan.c:586 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.503: 116342619: ../libfprint/drivers/elan.c:315 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.503: 116342632: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.504: 116343684: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.505: 116344764: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.506: 116345805: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.507: 116346821: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.508: 116347831: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.509: 116348831: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.510: 116349904: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.511: 116350916: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.512: 116351953: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.513: 116352921: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.514: 116354051: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.515: 116355032: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-elan-DEBUG: 05:38:15.516: 116356154: ../libfprint/drivers/elan.c:272 170s (process:3188): libfprint-assembling-DEBUG: 05:38:15.689: calc delta completed in 0.171647 secs 170s (process:3188): libfprint-assembling-DEBUG: 05:38:15.862: calc delta completed in 0.172607 secs 170s (process:3188): libfprint-assembling-DEBUG: 05:38:15.862: errors: 133465 rev: 143589 171s (process:3188): libfprint-assembling-DEBUG: 05:38:16.032: calc delta completed in 0.169930 secs 171s (process:3188): libfprint-assembling-DEBUG: 05:38:16.032: height is 225 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.032: Image device captured an image 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.033: 116872665: ../libfprint/drivers/elan.c:960 171s (process:3188): libfprint-device-DEBUG: 05:38:16.033: Device reported finger status change: FP_FINGER_STATUS_PRESENT 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.033: 116872682: ../libfprint/drivers/elan.c:507 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.033: 116872687: ../libfprint/drivers/elan.c:100 171s (process:3188): libfprint-SSM-DEBUG: 05:38:16.033: [elan] STOP_CAPTURE_NUM_STATES entering state 0 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.033: 116872705: ../libfprint/drivers/elan.c:466 171s (process:3188): libfprint-device-DEBUG: 05:38:16.036: Updated temperature model after 0.60 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876634: ../libfprint/drivers/elan.c:346 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876644: ../libfprint/drivers/elan.c:366 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876649: ../libfprint/drivers/elan.c:379 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: skipping read, not expecting anything 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876663: ../libfprint/drivers/elan.c:335 171s (process:3188): libfprint-SSM-DEBUG: 05:38:16.037: [elan] STOP_CAPTURE_NUM_STATES completed successfully 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876680: ../libfprint/drivers/elan.c:483 171s (process:3188): libfprint-device-DEBUG: 05:38:16.037: Device reported finger status change: FP_FINGER_STATUS_NONE 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.037: Image device reported finger status: off 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876735: ../libfprint/drivers/elan.c:960 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.037: Deactivating image device 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876755: ../libfprint/drivers/elan.c:960 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876769: ../libfprint/drivers/elan.c:975 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.037: Image device deactivation completed 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.037: 116876799: ../libfprint/drivers/elan.c:960 171s (process:3188): libfprint-image-DEBUG: 05:38:16.054: Minutiae scan completed in 0.021158 secs 171s (process:3188): libfprint-device-DEBUG: 05:38:16.054: Device reported capture completion 171s (process:3188): libfprint-device-DEBUG: 05:38:16.054: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 171s (process:3188): libfprint-device-DEBUG: 05:38:16.054: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.055: 116894606: ../libfprint/drivers/elan.c:939 171s (process:3188): libfprint-elan-DEBUG: 05:38:16.055: 116894617: ../libfprint/drivers/elan.c:100 171s (process:3188): libfprint-image_device-DEBUG: 05:38:16.055: Image device close completed 171s (process:3188): libfprint-device-DEBUG: 05:38:16.055: Device reported close completion 171s (process:3188): libfprint-device-DEBUG: 05:38:16.055: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s (process:3188): libfprint-device-DEBUG: 05:38:16.055: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ** (umockdev-run:3184): DEBUG: 05:38:16.200: umockdev.vala:154: Removing test bed /tmp/umockdev.XJ5I22 171s (umockdev-run:3184): GLib-DEBUG: 05:38:16.207: unsetenv() is not thread-safe and should not be used after threads are created 171s Comparing PNGs /tmp/libfprint-umockdev-test-vddvspfe/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 171s PASS: libfprint-2/driver-elan-cobo.test 171s Running test: libfprint-2/fpi-device.test 171s TAP version 14 171s # random seed: R02Secce5d23f1cbff683b95cb0ed575aafd 171s 1..97 171s # Start of driver tests 171s ok 1 /driver/get_driver 171s ok 2 /driver/get_device_id 171s ok 3 /driver/get_name 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 4 /driver/is_open 171s ok 5 /driver/get_nr_enroll_stages 171s ok 6 /driver/set_nr_enroll_stages 171s ok 7 /driver/supports_identify 171s ok 8 /driver/supports_capture 171s ok 9 /driver/has_storage 171s ok 10 /driver/do_not_support_identify 171s ok 11 /driver/do_not_support_capture 171s ok 12 /driver/has_not_storage 171s ok 13 /driver/get_usb_device 171s ok 14 /driver/get_virtual_env 171s ok 15 /driver/get_driver_data 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 171s # 171s # libfprint-device-DEBUG: Device reported probe completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 16 /driver/initial_features 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 171s # 171s # libfprint-device-DEBUG: Device reported probe completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 17 /driver/probe 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 18 /driver/open 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 19 /driver/close 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 171s # 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 20 /driver/enroll 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 21 /driver/verify 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 22 /driver/identify 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 171s # 171s # libfprint-device-DEBUG: Device reported capture completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 23 /driver/capture 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 171s # 171s # libfprint-device-DEBUG: Device reported listing completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 24 /driver/list 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 171s # 171s # libfprint-device-DEBUG: Device reported deletion completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 25 /driver/delete 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 171s # 171s # libfprint-device-DEBUG: Device reported deletion completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 26 /driver/clear_storage 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 171s # 171s # libfprint-device-DEBUG: Device reported deletion completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 27 /driver/cancel 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 28 /driver/critical 171s ok 29 /driver/get_current_action 171s ok 30 /driver/timeout 171s ok 31 /driver/error_types 171s ok 32 /driver/retry_error_types 171s # Start of get_scan_type tests 171s ok 33 /driver/get_scan_type/press 171s ok 34 /driver/get_scan_type/swipe 171s # End of get_scan_type tests 171s # Start of set_scan_type tests 171s ok 35 /driver/set_scan_type/press 171s ok 36 /driver/set_scan_type/swipe 171s # End of set_scan_type tests 171s # Start of finger_status tests 171s ok 37 /driver/finger_status/inactive 171s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 171s ok 38 /driver/finger_status/waiting 171s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 171s ok 39 /driver/finger_status/present 171s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 171s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 171s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 171s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 171s ok 40 /driver/finger_status/changes 171s # End of finger_status tests 171s # Start of features tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 171s # 171s # libfprint-device-DEBUG: Device reported probe completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 41 /driver/features/probe_updates 171s # End of features tests 171s # Start of initial_features tests 171s ok 42 /driver/initial_features/none 171s ok 43 /driver/initial_features/no_capture 171s ok 44 /driver/initial_features/no_verify 171s ok 45 /driver/initial_features/no_identify 171s ok 46 /driver/initial_features/no_storage 171s ok 47 /driver/initial_features/no_list 171s ok 48 /driver/initial_features/no_delete 171s ok 49 /driver/initial_features/no_clear 171s # End of initial_features tests 171s # Start of probe tests 171s # libfprint-device-DEBUG: Device reported probe completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 50 /driver/probe/error 171s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 171s # libfprint-device-DEBUG: Device reported probe completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 51 /driver/probe/action_error 171s # End of probe tests 171s # Start of open tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 52 /driver/open/error 171s # End of open tests 171s # Start of close tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 53 /driver/close/error 171s # End of close tests 171s # Start of enroll tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 171s # 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 54 /driver/enroll/error 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported enroll progress, reported 1918199180 of 1427960293 have been completed 171s # libfprint-device-DEBUG: Device reported enroll progress, reported 1476806878 of 1427960293 have been completed 171s # libfprint-device-DEBUG: Device reported enroll progress, reported 1570331903 of 1427960293 have been completed 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 171s # 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 55 /driver/enroll/progress 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 171s # 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 56 /driver/enroll/update_nbis 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 57 /driver/enroll/update_nbis_wrong_device 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 58 /driver/enroll/update_nbis_wrong_driver 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 59 /driver/enroll/update_nbis_missing_feature 171s # Start of error tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported enroll completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 60 /driver/enroll/error/no_print 171s # End of error tests 171s # End of enroll tests 171s # Start of verify tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 61 /driver/verify/fail 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 62 /driver/verify/retry 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 171s # 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 63 /driver/verify/error 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 64 /driver/verify/not_supported 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 65 /driver/verify/report_no_cb 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 66 /driver/verify/not_reported 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported verify result 171s # libfprint-device-DEBUG: Device reported verify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 67 /driver/verify/complete_retry 171s # End of verify tests 171s # Start of identify tests 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 171s ok 68 /driver/identify/fail 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 69 /driver/identify/retry 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 171s ok 70 /driver/identify/error 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 171s ok 71 /driver/identify/not_reported 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 72 /driver/identify/complete_retry 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 73 /driver/identify/report_no_cb 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 74 /driver/identify/suspend_continues 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify result 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 75 /driver/identify/suspend_succeeds 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 171s # 171s # libfprint-device-DEBUG: Device reported identify completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 171s ok 76 /driver/identify/suspend_busy_error 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 171s # 171s # libfprint-device-DEBUG: Device reported close completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s ok 77 /driver/identify/suspend_while_idle 171s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 171s # 171s # libfprint-device-DEBUG: Device reported open completion 171s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 171s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 173s Executing: libfprint-2/fpi-device.test 173s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 173s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 173s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 173s # 173s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 173s # 173s # libfprint-device-DEBUG: Device reported identify completion 173s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 173s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 173s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 173s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 175s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 178s Executing: libfprint-2/fpi-device.test 178s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 178s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 178s # 178s # libfprint-device-DEBUG: Device reported close completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s ok 78 /driver/identify/warmup_cooldown 178s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 178s # End of identify tests 178s # Start of capture tests 178s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 178s # 178s # libfprint-device-DEBUG: Device reported open completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 178s # 178s # libfprint-device-DEBUG: Device reported close completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s ok 79 /driver/capture/not_supported 178s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 178s # 178s # libfprint-device-DEBUG: Device reported open completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 179s # 179s # libfprint-device-DEBUG: Device reported capture completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 80 /driver/capture/error 179s # End of capture tests 179s # Start of list tests 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 179s # 179s # libfprint-device-DEBUG: Device reported listing completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 81 /driver/list/error 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 82 /driver/list/no_storage 179s # End of list tests 179s # Start of delete tests 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 179s # 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 83 /driver/delete/error 179s # End of delete tests 179s # Start of clear_storage tests 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 179s # 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 84 /driver/clear_storage/error 179s # End of clear_storage tests 179s # Start of cancel tests 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 179s # 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 85 /driver/cancel/fail 179s # End of cancel tests 179s # Start of get_current_action tests 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 86 /driver/get_current_action/open 179s # End of get_current_action tests 179s # Start of get_cancellable tests 179s ok 87 /driver/get_cancellable/error 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 88 /driver/get_cancellable/open 179s # Start of open tests 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 89 /driver/get_cancellable/open/internal 179s # End of open tests 179s # End of get_cancellable tests 179s # Start of action_is_cancelled tests 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 90 /driver/action_is_cancelled/open 179s ok 91 /driver/action_is_cancelled/error 179s # Start of open tests 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 92 /driver/action_is_cancelled/open/internal 179s # End of open tests 179s # End of action_is_cancelled tests 179s # Start of complete_action tests 179s # Start of all tests 179s ok 93 /driver/complete_action/all/error 179s # End of all tests 179s # End of complete_action tests 179s # Start of action_error tests 179s ok 94 /driver/action_error/error 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 179s # libfprint-device-DEBUG: Device reported enroll completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 179s # libfprint-device-DEBUG: Device reported verify completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 179s # libfprint-device-DEBUG: Device reported identify completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 179s # libfprint-device-DEBUG: Device reported capture completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 179s # libfprint-device-DEBUG: Device reported listing completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 95 /driver/action_error/all 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 179s # 179s # libfprint-device-DEBUG: Device reported open completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 179s # 179s # libfprint-device-DEBUG: Device reported enroll completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 179s # 179s # libfprint-device-DEBUG: Device reported verify completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 179s # 179s # libfprint-device-DEBUG: Device reported identify completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 179s # 179s # libfprint-device-DEBUG: Device reported capture completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 179s # 179s # libfprint-device-DEBUG: Device reported listing completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 179s # 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 179s # 179s # libfprint-device-DEBUG: Device reported deletion completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 179s # 179s # libfprint-device-DEBUG: Device reported close completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 179s ok 96 /driver/action_error/fail 179s # End of action_error tests 179s # Start of timeout tests 179s ok 97 /driver/timeout/cancelled 179s # End of timeout tests 179s # End of driver tests 179s PASS: libfprint-2/fpi-device.test 179s Running test: libfprint-2/driver-elanspi.test 179s ** (umockdev-run:3201): DEBUG: 05:38:24.026: umockdev.vala:127: Created udev test bed /tmp/umockdev.G9CC22 179s ** (umockdev-run:3201): DEBUG: 05:38:24.026: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 179s ** (umockdev-run:3201): DEBUG: 05:38:24.027: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 (subsystem spidev) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.028: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.G9CC22/dev/spidev0.0: got pty /dev/pts/0 179s ** (umockdev-run:3201): DEBUG: 05:38:24.028: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.G9CC22/dev/.ptymap/_dev_pts_0 179s ** (umockdev-run:3201): DEBUG: 05:38:24.028: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 179s ** (umockdev-run:3201): DEBUG: 05:38:24.029: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.031: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 179s ** (umockdev-run:3201): DEBUG: 05:38:24.032: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.034: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 179s ** (umockdev-run:3201): DEBUG: 05:38:24.034: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.035: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2 179s ** (umockdev-run:3201): DEBUG: 05:38:24.035: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.037: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 179s ** (umockdev-run:3201): DEBUG: 05:38:24.038: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 (subsystem hidraw) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.039: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.G9CC22/dev/hidraw0: got pty /dev/pts/1 179s ** (umockdev-run:3201): DEBUG: 05:38:24.039: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.G9CC22/dev/.ptymap/_dev_pts_1 179s ** (umockdev-run:3201): DEBUG: 05:38:24.039: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 179s ** (umockdev-run:3201): DEBUG: 05:38:24.039: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 (subsystem hid) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.040: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 179s ** (umockdev-run:3201): DEBUG: 05:38:24.040: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.041: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 179s ** (umockdev-run:3201): DEBUG: 05:38:24.041: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.042: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 179s ** (umockdev-run:3201): DEBUG: 05:38:24.042: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 179s ** (umockdev-run:3201): DEBUG: 05:38:24.042: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1 179s ** (umockdev-run:3201): DEBUG: 05:38:24.043: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 179s (umockdev-run:3201): GLib-GIO-DEBUG: 05:38:24.045: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 179s (process:3205): libfprint-context-DEBUG: 05:38:24.174: Initializing FpContext (libfprint version 1.94.9+tod1) 179s (process:3205): libfprint-tod-DEBUG: 05:38:24.174: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 179s libfprint-Message: 05:38:24.179: Failed to read spidev block size, using 4096 179s (process:3205): libfprint-device-DEBUG: 05:38:24.178: Device reported probe completion 179s (process:3205): libfprint-device-DEBUG: 05:38:24.178: Completing action FPI_DEVICE_ACTION_PROBE in idle! 179s (process:3205): libfprint-device-DEBUG: 05:38:24.178: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.179: 125018498: ../libfprint/drivers/elanspi.c:1562 179s (process:3205): libfprint-image_device-DEBUG: 05:38:24.179: Image device open completed 179s (process:3205): libfprint-device-DEBUG: 05:38:24.179: Device reported open completion 179s (process:3205): libfprint-device-DEBUG: 05:38:24.179: Completing action FPI_DEVICE_ACTION_OPEN in idle! 179s (process:3205): libfprint-device-DEBUG: 05:38:24.179: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:3205): libfprint-device-DEBUG: 05:38:24.179: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s (process:3205): libfprint-image_device-DEBUG: 05:38:24.179: Activating image device 179s (process:3205): libfprint-image_device-DEBUG: 05:38:24.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.179: [elanspi] ELANSPI_INIT_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.180: [elanspi] ELANSPI_INIT_NSTATES entering state 1 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.180: got status 81 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.180: sync hw reset 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.181: [elanspi] ELANSPI_INIT_NSTATES entering state 2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.185: [elanspi] ELANSPI_INIT_NSTATES entering state 3 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.185: sw reset ok 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.185: [elanspi] ELANSPI_INIT_NSTATES entering state 4 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.185: raw height = 96 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.186: [elanspi] ELANSPI_INIT_NSTATES entering state 5 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.186: raw width = 96 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.186: [elanspi] ELANSPI_INIT_NSTATES entering state 6 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.186: raw reg17 = 175 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.187: [elanspi] ELANSPI_INIT_NSTATES entering state 7 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.187: raw version = 09 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.187: after hardcoded lookup; 96x96, version 1 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.187: found sensor ID 6 => [eFSA96SA] (96 x 96) 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.187: [elanspi] ELANSPI_INIT_NSTATES entering state 8 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.191: [elanspi] ELANSPI_INIT_NSTATES entering state 9 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.192: [elanspi] ELANSPI_INIT_NSTATES entering state 10 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.193: [elanspi] ELANSPI_INIT_NSTATES entering state 11 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.193: [elanspi] ELANSPI_INIT_NSTATES entering state 12 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.193: [elanspi] ELANSPI_INIT_NSTATES entering state 13 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.194: [elanspi] ELANSPI_INIT_NSTATES entering state 14 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.194: [elanspi] ELANSPI_INIT_NSTATES entering state 17 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.194: got vcm mode = 2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.194: [elanspi] ELANSPI_INIT_NSTATES entering state 18 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.194: [elanspi] ELANSPI_INIT_NSTATES entering state 19 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.194: starting calibrate 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.194: [elanspi] old calibrate entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.196: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.197: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.197: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.197: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.197: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.198: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.198: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.198: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.198: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.198: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.198: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.199: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.199: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.199: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.199: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.199: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.200: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.200: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.200: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.200: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.200: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.200: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.201: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.201: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.201: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.201: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.201: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.202: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.203: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.203: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.203: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.203: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.203: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.203: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.204: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.204: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.204: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.204: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.205: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.278: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.278: dac init is 0x29 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.278: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-device-DEBUG: 05:38:24.279: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.342: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.343: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.416: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.416: calibration ok, saving bg image 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.417: [elanspi] old calibrate completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.417: [elanspi] ELANSPI_INIT_NSTATES entering state 20 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.417: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.491: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.491: [elanspi] ELANSPI_INIT_NSTATES entering state 21 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.491: [elanspi] ELANSPI_INIT_NSTATES completed successfully 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.492: 125331478: ../libfprint/drivers/elanspi.c:1596 179s (process:3205): libfprint-image_device-DEBUG: 05:38:24.492: Image device activation completed 179s (process:3205): libfprint-image_device-DEBUG: 05:38:24.492: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 179s (process:3205): libfprint-image_device-DEBUG: 05:38:24.492: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.492: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.492: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.492: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.492: started capturer 179s (process:3205): libfprint-device-DEBUG: 05:38:24.492: Device reported finger status change: FP_FINGER_STATUS_NEEDED 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.564: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.564: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.565: stddev=933d, ip=40, is_fp=0, is_empty=2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.565: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.565: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.652: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.652: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.653: stddev=829d, ip=48, is_fp=0, is_empty=2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.653: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.653: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.735: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.735: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.736: stddev=1307d, ip=37, is_fp=0, is_empty=2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.736: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.736: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.824: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.824: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.824: stddev=1163d, ip=38, is_fp=0, is_empty=2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.825: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.825: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.907: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.907: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.908: stddev=960d, ip=43, is_fp=0, is_empty=2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.908: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.908: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.974: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.974: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 179s (process:3205): libfprint-elanspi-DEBUG: 05:38:24.974: stddev=879d, ip=41, is_fp=0, is_empty=2 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.974: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 179s (process:3205): libfprint-SSM-DEBUG: 05:38:24.974: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.037: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.037: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.038: stddev=925d, ip=44, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.038: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.038: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.109: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.109: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.110: stddev=1244d, ip=37, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.110: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.110: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.197: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.197: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.198: stddev=709d, ip=48, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.198: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.198: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.264: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.264: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.265: stddev=553d, ip=54, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.265: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.265: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.329: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.330: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.330: stddev=904d, ip=44, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.330: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.330: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.394: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.394: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.395: stddev=951d, ip=46, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.395: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.395: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.459: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.459: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.460: stddev=795d, ip=44, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.460: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.460: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.543: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.543: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.543: stddev=985d, ip=41, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.543: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.543: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.622: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.622: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.623: stddev=938d, ip=40, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.623: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.623: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.711: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.711: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.712: stddev=846d, ip=40, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.712: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.712: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.801: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.801: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.802: stddev=693d, ip=56, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.802: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.802: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.891: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.892: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.892: stddev=777d, ip=50, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.892: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.892: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.967: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.967: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 180s (process:3205): libfprint-elanspi-DEBUG: 05:38:25.967: stddev=824d, ip=45, is_fp=0, is_empty=2 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.967: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 180s (process:3205): libfprint-SSM-DEBUG: 05:38:25.967: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.049: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.049: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.049: stddev=521d, ip=50, is_fp=0, is_empty=2 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.049: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.049: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.125: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.125: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.125: stddev=670d, ip=47, is_fp=0, is_empty=2 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.125: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.125: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.206: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.207: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.207: stddev=1262d, ip=39, is_fp=0, is_empty=2 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.207: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.207: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.298: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.298: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.298: stddev=912d, ip=42, is_fp=0, is_empty=2 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.298: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.298: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.384: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.384: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.385: stddev=1402d, ip=37, is_fp=0, is_empty=2 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.385: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.385: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.475: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.475: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.476: stddev=1530d, ip=32, is_fp=0, is_empty=2 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.476: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.476: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.561: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.561: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.562: stddev=718159d, ip=6, is_fp=1, is_empty=0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.562: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.562: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.673: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.673: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.674: stddev=400929d, ip=0, is_fp=2, is_empty=0 181s (process:3205): libfprint-device-DEBUG: 05:38:26.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 181s (process:3205): libfprint-image_device-DEBUG: 05:38:26.675: Image device reported finger status: on 181s (process:3205): libfprint-image_device-DEBUG: 05:38:26.675: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.675: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.675: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.768: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.768: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.769: stddev=346514d, ip=0, is_fp=1, is_empty=0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.770: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.770: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.861: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.861: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.862: stddev=324160d, ip=0, is_fp=1, is_empty=0 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.863: diff = 107344 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.863: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.863: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.942: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.942: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.942: stddev=339430d, ip=0, is_fp=1, is_empty=0 181s (process:3205): libfprint-elanspi-DEBUG: 05:38:26.944: diff = 246471 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.944: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 181s (process:3205): libfprint-SSM-DEBUG: 05:38:26.944: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.027: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.028: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.028: stddev=334711d, ip=0, is_fp=1, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.030: diff = 73010 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.030: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.030: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.108: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.108: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.109: stddev=317574d, ip=0, is_fp=1, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.110: diff = 58831 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.111: ignoring b.c. difference is too small 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.111: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.111: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.193: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.193: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.194: stddev=285577d, ip=0, is_fp=1, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.196: diff = 241923 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.196: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.196: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.279: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.279: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.280: stddev=417772d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.281: diff = 254823 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.281: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.281: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.360: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.360: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.361: stddev=541148d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.362: diff = 290922 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.362: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.362: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.447: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.447: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.448: stddev=580192d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.450: diff = 332283 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.450: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.450: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.539: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.539: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.540: stddev=484527d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.542: diff = 325141 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.542: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.542: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.636: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.636: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.636: stddev=482100d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.638: diff = 337412 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.638: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.638: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.731: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.731: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.732: stddev=558238d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.733: diff = 342841 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.733: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.733: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.818: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.818: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.819: stddev=572990d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.821: diff = 352690 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.821: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.821: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.909: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.909: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.910: stddev=575411d, ip=0, is_fp=2, is_empty=0 182s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.912: diff = 365537 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.912: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 182s (process:3205): libfprint-SSM-DEBUG: 05:38:27.912: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:27.987: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:27.987: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.988: stddev=578482d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:27.989: diff = 342041 183s (process:3205): libfprint-SSM-DEBUG: 05:38:27.989: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:27.989: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.075: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.075: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.076: stddev=572686d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.077: diff = 421037 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.078: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.078: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.159: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.159: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.160: stddev=465498d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.162: diff = 404640 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.162: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.162: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s Executing: libfprint-2/driver-elanspi.test 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.244: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.244: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.245: stddev=410135d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.247: diff = 347658 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.247: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.324: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.324: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.325: stddev=493239d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.327: diff = 344237 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.327: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.327: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.410: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.410: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.411: stddev=553028d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.412: diff = 419597 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.412: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.412: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.491: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.491: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.492: stddev=574502d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.493: diff = 408934 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.493: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.493: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.573: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.573: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.574: stddev=645815d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.575: diff = 409198 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.575: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.575: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.659: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.659: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.659: stddev=677451d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.660: diff = 429666 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.661: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.661: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.741: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 183s (process:3205): libfprint-SSM-DEBUG: 05:38:28.742: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.742: stddev=634407d, ip=0, is_fp=2, is_empty=0 183s (process:3205): libfprint-elanspi-DEBUG: 05:38:28.742: have enough frames, exiting now 183s (process:3205): libfprint-assembling-DEBUG: 05:38:28.864: calc delta completed in 0.121385 secs 184s (process:3205): libfprint-assembling-DEBUG: 05:38:28.990: calc delta completed in 0.125971 secs 184s (process:3205): libfprint-assembling-DEBUG: 05:38:28.990: errors: 86516 rev: 170625 184s (process:3205): libfprint-assembling-DEBUG: 05:38:29.112: calc delta completed in 0.122161 secs 184s (process:3205): libfprint-assembling-DEBUG: 05:38:29.112: height is 246 184s (process:3205): libfprint-image_device-DEBUG: 05:38:29.114: Image device captured an image 184s (process:3205): libfprint-image_device-DEBUG: 05:38:29.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:3205): libfprint-device-DEBUG: 05:38:29.114: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.114: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.114: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.168: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.168: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.169: stddev=593525d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.169: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.169: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-image-DEBUG: 05:38:29.170: Minutiae scan completed in 0.055924 secs 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.233: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.233: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.233: stddev=610651d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.233: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.233: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.306: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.307: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.307: stddev=505673d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.307: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.307: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.380: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.380: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.381: stddev=537580d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.381: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.381: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.463: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.463: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.463: stddev=520750d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.463: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.463: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.557: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.557: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.557: stddev=468008d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.558: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.558: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.645: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.645: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.645: stddev=477058d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.645: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.645: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.731: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.731: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.732: stddev=460178d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.732: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.732: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.824: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.824: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.825: stddev=538508d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.825: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.825: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.911: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.911: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 184s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.912: stddev=661673d, ip=0, is_fp=2, is_empty=0 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.912: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 184s (process:3205): libfprint-SSM-DEBUG: 05:38:29.912: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:29.993: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:29.993: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:29.993: stddev=764706d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:29.993: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:29.993: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.086: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.087: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.087: stddev=806415d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.087: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.087: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.184: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.184: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.185: stddev=806649d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.185: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.185: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.272: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.272: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.273: stddev=822567d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.273: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.273: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.369: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.369: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.369: stddev=1017068d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.369: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.369: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.449: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.449: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.450: stddev=1004196d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.450: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.450: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.537: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.537: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.537: stddev=963655d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.537: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.537: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.625: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.625: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.625: stddev=880521d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.625: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.625: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.719: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.719: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.720: stddev=1135372d, ip=0, is_fp=2, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.720: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.720: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.818: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.818: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.819: stddev=1093450d, ip=3, is_fp=1, is_empty=0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.819: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.819: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.914: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.914: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 185s (process:3205): libfprint-elanspi-DEBUG: 05:38:30.915: stddev=41090d, ip=8, is_fp=0, is_empty=2 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.915: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 185s (process:3205): libfprint-SSM-DEBUG: 05:38:30.915: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 186s (process:3205): libfprint-SSM-DEBUG: 05:38:31.004: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 186s (process:3205): libfprint-SSM-DEBUG: 05:38:31.004: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 186s (process:3205): libfprint-elanspi-DEBUG: 05:38:31.005: stddev=6836d, ip=13, is_fp=0, is_empty=2 186s (process:3205): libfprint-device-DEBUG: 05:38:31.005: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Image device reported finger status: off 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Deactivating image device 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Image device deactivation completed 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 186s (process:3205): libfprint-device-DEBUG: 05:38:31.005: Device reported capture completion 186s (process:3205): libfprint-SSM-DEBUG: 05:38:31.005: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 186s (process:3205): libfprint-device-DEBUG: 05:38:31.005: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 186s (process:3205): libfprint-device-DEBUG: 05:38:31.005: Updated temperature model after 6.73 seconds, ratio 0.27 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:3205): libfprint-image_device-DEBUG: 05:38:31.005: Image device close completed 186s (process:3205): libfprint-device-DEBUG: 05:38:31.006: Device reported close completion 186s (process:3205): libfprint-device-DEBUG: 05:38:31.006: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 186s (process:3205): libfprint-device-DEBUG: 05:38:31.006: Updated temperature model after 0.00 seconds, ratio 0.30 -> 0.30, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s ** (umockdev-run:3201): DEBUG: 05:38:31.388: umockdev.vala:154: Removing test bed /tmp/umockdev.G9CC22 186s (umockdev-run:3201): GLib-DEBUG: 05:38:31.401: unsetenv() is not thread-safe and should not be used after threads are created 186s Comparing PNGs /tmp/libfprint-umockdev-test-h_b0oy03/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 186s PASS: libfprint-2/driver-elanspi.test 186s Running test: libfprint-2/driver-goodixmoc.test 186s ** (umockdev-run:3216): DEBUG: 05:38:31.532: umockdev.vala:127: Created udev test bed /tmp/umockdev.9AS112 186s ** (umockdev-run:3216): DEBUG: 05:38:31.533: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 186s ** (umockdev-run:3216): DEBUG: 05:38:31.535: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 186s ** (umockdev-run:3216): DEBUG: 05:38:31.542: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9AS112/dev/bus/usb/003/004 186s ** (umockdev-run:3216): DEBUG: 05:38:31.542: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 186s ** (umockdev-run:3216): DEBUG: 05:38:31.545: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 186s ** (umockdev-run:3216): DEBUG: 05:38:31.550: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9AS112/dev/bus/usb/003/001 186s ** (umockdev-run:3216): DEBUG: 05:38:31.551: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 186s ** (umockdev-run:3216): DEBUG: 05:38:31.552: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 186s (process:3220): libfprint-context-DEBUG: 05:38:31.670: Initializing FpContext (libfprint version 1.94.9+tod1) 186s (process:3220): libfprint-tod-DEBUG: 05:38:31.670: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 186s (process:3220): libfprint-context-DEBUG: 05:38:31.674: No driver found for USB device 1D6B:0002 186s (process:3220): libfprint-device-DEBUG: 05:38:31.676: Device reported probe completion 186s (process:3220): libfprint-device-DEBUG: 05:38:31.676: Completing action FPI_DEVICE_ACTION_PROBE in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.676: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.678: [goodixmoc] FP_INIT_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.678: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.679: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.679: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.680: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.681: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.681: Firmware type: APP 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.682: Firmware version: 01000274 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.682: [goodixmoc] FP_INIT_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.682: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.682: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.682: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.683: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.683: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.684: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.685: [goodixmoc] FP_INIT_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.685: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.685: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.685: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.686: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.687: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.687: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.688: [goodixmoc] FP_INIT_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.688: Device reported open completion 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.688: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.688: Completing action FPI_DEVICE_ACTION_OPEN in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.688: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.688: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.689: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.690: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.690: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.691: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.692: Successfully cleared storage 186s (process:3220): libfprint-device-DEBUG: 05:38:31.692: Device reported deletion completion 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.692: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.692: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.692: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.693: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.693: [goodixmoc] enroll entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.693: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.694: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.694: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.695: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.696: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.696: [goodixmoc] enroll entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.697: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.697: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.697: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.698: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.698: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.699: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.700: [goodixmoc] enroll entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.700: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.700: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.700: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.701: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.702: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.702: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.703: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-device-DEBUG: 05:38:31.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.703: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.703: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.704: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.704: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.705: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.705: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.706: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.706: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.706: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.707: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.707: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.708: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.709: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.709: Device reported enroll progress, reported 1 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.710: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.710: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.710: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.710: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.711: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.711: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.712: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.713: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.713: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.713: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.713: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.714: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.714: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.715: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.716: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.716: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.716: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.716: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.717: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.717: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.718: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.719: Device reported enroll progress, reported 2 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.719: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.719: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.719: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.719: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.720: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.721: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.721: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.722: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.722: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.722: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.722: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.723: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.724: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.724: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.725: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.725: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.725: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.725: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.726: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.727: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.727: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.728: Device reported enroll progress, reported 3 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.728: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.728: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.728: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.729: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.729: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.730: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.730: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.731: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.731: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.731: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.732: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.732: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.733: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.737: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.738: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.738: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.738: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.739: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.739: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.740: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.740: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.741: Device reported enroll progress, reported 4 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.741: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.741: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.741: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.742: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.742: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.743: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.744: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.744: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.744: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.745: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.745: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.745: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.746: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.748: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.749: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.749: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.749: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.749: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.749: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.750: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.751: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.752: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.752: Device reported enroll progress, reported 5 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.753: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.753: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.753: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.753: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.754: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.754: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.755: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.756: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.756: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.756: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.756: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.757: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.761: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.762: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.764: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.765: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.765: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.766: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.767: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.768: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.769: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.770: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.770: Device reported enroll progress, reported 6 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.771: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.771: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.771: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.771: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.772: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.773: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.777: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.778: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.778: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.778: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.778: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.779: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.780: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.780: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.781: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.781: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.781: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.782: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.782: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.783: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.783: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.784: Device reported enroll progress, reported 7 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.784: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.784: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.785: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.785: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.786: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.786: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.787: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.787: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.787: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.787: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.788: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.788: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.789: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.789: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.790: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.791: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.791: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.791: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.791: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.792: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.792: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.793: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.794: Device reported enroll progress, reported 8 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.794: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.794: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.794: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.794: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.795: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.795: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.796: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.797: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.797: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.797: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.797: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.798: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.798: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.799: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.800: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.800: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.800: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.800: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.801: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.801: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.802: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.803: Device reported enroll progress, reported 9 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.803: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.803: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.803: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.803: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.804: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.804: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.805: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.806: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.806: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.806: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.806: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.806: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.807: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.807: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.808: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.809: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.809: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.813: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.813: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.814: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.815: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.815: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.816: Device reported enroll progress, reported 10 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.816: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.816: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.816: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.816: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.817: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.818: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.819: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.819: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.819: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.819: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.820: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.820: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.821: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.822: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.823: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.823: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.823: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.824: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.824: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.825: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.825: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.826: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.827: Device reported enroll progress, reported 11 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.827: [goodixmoc] enroll entering state 5 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.827: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.827: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.827: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.829: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.829: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.830: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.831: [goodixmoc] enroll entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.831: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.831: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.831: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.832: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.832: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.833: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.833: [goodixmoc] enroll entering state 4 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.833: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.834: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.834: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.835: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.835: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.836: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.836: Device reported enroll progress, reported 12 of 12 have been completed 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.837: [goodixmoc] enroll entering state 6 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.837: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.837: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.837: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.838: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.838: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.839: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.840: [goodixmoc] enroll entering state 7 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.840: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.840: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.840: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.840: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.841: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.841: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.842: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.843: [goodixmoc] enroll entering state 8 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.843: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.843: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.843: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.844: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.844: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.845: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.846: [goodixmoc] enroll completed successfully 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.846: Enrollment complete! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.846: Device reported enroll completion 186s (process:3220): libfprint-device-DEBUG: 05:38:31.846: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:3220): libfprint-device-DEBUG: 05:38:31.846: Print for finger FP_FINGER_UNKNOWN enrolled 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.846: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.846: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.846: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.846: 132685933: ../libfprint/drivers/goodixmoc/goodix.c:1556 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.846: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.847: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.847: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.848: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.848: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.849: Query complete! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.849: Device reported listing completion 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.849: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.849: Completing action FPI_DEVICE_ACTION_LIST in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.849: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.850: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.850: [goodixmoc] verify entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.850: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.850: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.851: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.851: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.852: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.853: [goodixmoc] verify entering state 1 186s (process:3220): libfprint-device-DEBUG: 05:38:31.853: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.853: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.854: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.854: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.855: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.855: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.856: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.856: [goodixmoc] verify entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.856: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.857: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.857: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.857: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.858: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.859: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-DEBUG: 05:38:31.859: match, score: 28, study: 0 186s (process:3220): libfprint-device-DEBUG: 05:38:31.860: Device reported verify result 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.860: [goodixmoc] verify entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.860: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.860: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.860: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.861: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.861: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.862: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.863: [goodixmoc] verify completed successfully 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.863: Verify complete! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.863: Device reported verify completion 186s (process:3220): libfprint-device-DEBUG: 05:38:31.863: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.863: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.863: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.863: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.863: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.863: [goodixmoc] verify entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.863: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.864: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.864: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.865: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.866: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.866: [goodixmoc] verify entering state 1 186s (process:3220): libfprint-device-DEBUG: 05:38:31.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.866: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.869: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.869: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.870: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.871: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.871: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-device-DEBUG: 05:38:31.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.872: [goodixmoc] verify entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.872: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.872: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.873: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.873: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.874: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.874: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-DEBUG: 05:38:31.875: match, score: 35, study: 0 186s (process:3220): libfprint-device-DEBUG: 05:38:31.876: Device reported identify result 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.876: [goodixmoc] verify entering state 3 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.876: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.876: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.877: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.877: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.878: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.879: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.879: [goodixmoc] verify completed successfully 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.879: Verify complete! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.879: Device reported identify completion 186s (process:3220): libfprint-device-DEBUG: 05:38:31.879: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.879: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.879: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.879: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.880: [goodixmoc] FP_CMD_NUM_STATES entering state 0 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.881: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.882: [goodixmoc] FP_CMD_NUM_STATES entering state 1 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.882: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.883: [goodixmoc] FP_CMD_NUM_STATES entering state 2 186s (process:3220): libfprint-goodixmoc-DEBUG: 05:38:31.884: Successfully deleted enrolled user 186s (process:3220): libfprint-device-DEBUG: 05:38:31.884: Device reported deletion completion 186s (process:3220): libfprint-SSM-DEBUG: 05:38:31.884: [goodixmoc] FP_CMD_NUM_STATES completed successfully 186s (process:3220): libfprint-device-DEBUG: 05:38:31.884: Completing action FPI_DEVICE_ACTION_DELETE in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.884: Not updating temperature model, device can run continuously! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.884: Device reported close completion 186s (process:3220): libfprint-device-DEBUG: 05:38:31.885: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 186s (process:3220): libfprint-device-DEBUG: 05:38:31.885: Not updating temperature model, device can run continuously! 186s enrolling 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 1, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 2, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 3, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 4, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 5, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 6, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 7, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 8, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 9, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 10, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 11, None, None, None) 186s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x6a724d18a340 (FpiDeviceGoodixMoc at 0x3a2497d0)>, 12, None, None, None) 186s enroll done 186s listing 186s listing done 186s verifying 186s verify done 186s async identifying 186s indentification_done: 186s deleting 186s delete done 186s ** (umockdev-run:3216): DEBUG: 05:38:31.905: umockdev.vala:154: Removing test bed /tmp/umockdev.9AS112 186s (umockdev-run:3216): GLib-DEBUG: 05:38:31.912: unsetenv() is not thread-safe and should not be used after threads are created 186s PASS: libfprint-2/driver-goodixmoc.test 186s Running test: libfprint-2/driver-nb1010.test 186s ** (umockdev-run:3228): DEBUG: 05:38:31.968: umockdev.vala:127: Created udev test bed /tmp/umockdev.GGFA22 186s ** (umockdev-run:3228): DEBUG: 05:38:31.969: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 186s ** (umockdev-run:3228): DEBUG: 05:38:31.974: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 187s ** (umockdev-run:3228): DEBUG: 05:38:31.978: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.GGFA22/dev/bus/usb/001/003 187s ** (umockdev-run:3228): DEBUG: 05:38:31.978: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 187s ** (umockdev-run:3228): DEBUG: 05:38:31.984: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 187s ** (umockdev-run:3228): DEBUG: 05:38:31.987: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.GGFA22/dev/bus/usb/001/001 187s ** (umockdev-run:3228): DEBUG: 05:38:31.988: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 187s ** (umockdev-run:3228): DEBUG: 05:38:31.990: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 187s ** (umockdev-run:3228): DEBUG: 05:38:31.992: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 187s ** (umockdev-run:3228): DEBUG: 05:38:31.993: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 187s (umockdev-run:3228): GLib-GIO-DEBUG: 05:38:31.997: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 187s (process:3232): libfprint-context-DEBUG: 05:38:32.102: Initializing FpContext (libfprint version 1.94.9+tod1) 187s (process:3232): libfprint-tod-DEBUG: 05:38:32.102: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:3232): libfprint-context-DEBUG: 05:38:32.105: No driver found for USB device 1D6B:0002 187s (process:3232): libfprint-device-DEBUG: 05:38:32.105: Device reported probe completion 187s (process:3232): libfprint-device-DEBUG: 05:38:32.105: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:3232): libfprint-device-DEBUG: 05:38:32.105: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.107: Image device open completed 187s (process:3232): libfprint-device-DEBUG: 05:38:32.107: Device reported open completion 187s (process:3232): libfprint-nb1010-DEBUG: 05:38:32.107: nb1010 Initialized 187s (process:3232): libfprint-device-DEBUG: 05:38:32.108: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:3232): libfprint-device-DEBUG: 05:38:32.108: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:3232): libfprint-device-DEBUG: 05:38:32.108: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.108: Activating image device 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.108: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.108: Image device activation completed 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.108: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.108: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.108: [nb1010] M_LOOP_NUM_STATES entering state 0 187s (process:3232): libfprint-device-DEBUG: 05:38:32.108: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3232): libfprint-nb1010-DEBUG: 05:38:32.108: nb1010 Activated 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.158: [nb1010] M_LOOP_NUM_STATES entering state 1 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.159: [nb1010] M_LOOP_NUM_STATES entering state 2 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.159: [nb1010] M_LOOP_NUM_STATES entering state 3 187s (process:3232): libfprint-device-DEBUG: 05:38:32.160: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.160: Image device reported finger status: on 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.161: [nb1010] M_LOOP_NUM_STATES entering state 4 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.162: [nb1010] M_LOOP_NUM_STATES entering state 5 187s (process:3232): libfprint-device-DEBUG: 05:38:32.208: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.229: [nb1010] M_LOOP_NUM_STATES entering state 6 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.230: Image device captured an image 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.230: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 187s (process:3232): libfprint-device-DEBUG: 05:38:32.230: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3232): libfprint-SSM-DEBUG: 05:38:32.231: [nb1010] M_LOOP_NUM_STATES completed successfully 187s (process:3232): libfprint-nb1010-DEBUG: 05:38:32.231: nb1010 ssm complete cb 187s (process:3232): libfprint-device-DEBUG: 05:38:32.231: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.231: Image device reported finger status: off 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.231: Deactivating image device 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.231: Image device deactivation completed 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 187s (process:3232): libfprint-nb1010-DEBUG: 05:38:32.232: nb1010 Deactivated 187s (process:3232): libfprint-image-DEBUG: 05:38:32.249: Minutiae scan completed in 0.017780 secs 187s (process:3232): libfprint-device-DEBUG: 05:38:32.249: Device reported capture completion 187s (process:3232): libfprint-device-DEBUG: 05:38:32.249: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 187s (process:3232): libfprint-device-DEBUG: 05:38:32.249: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:3232): libfprint-image_device-DEBUG: 05:38:32.250: Image device close completed 187s (process:3232): libfprint-device-DEBUG: 05:38:32.250: Device reported close completion 187s (process:3232): libfprint-nb1010-DEBUG: 05:38:32.250: nb1010 Deinitialized 187s (process:3232): libfprint-device-DEBUG: 05:38:32.250: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:3232): libfprint-device-DEBUG: 05:38:32.250: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s ** (umockdev-run:3228): DEBUG: 05:38:32.365: umockdev.vala:154: Removing test bed /tmp/umockdev.GGFA22 187s (umockdev-run:3228): GLib-DEBUG: 05:38:32.375: unsetenv() is not thread-safe and should not be used after threads are created 187s Comparing PNGs /tmp/libfprint-umockdev-test-5_3mqui2/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 187s PASS: libfprint-2/driver-nb1010.test 187s Running test: libfprint-2/driver-realtek-5816.test 187s ** (umockdev-run:3241): DEBUG: 05:38:32.448: umockdev.vala:127: Created udev test bed /tmp/umockdev.P5QL22 187s ** (umockdev-run:3241): DEBUG: 05:38:32.449: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 187s ** (umockdev-run:3241): DEBUG: 05:38:32.452: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 187s ** (umockdev-run:3241): DEBUG: 05:38:32.459: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.P5QL22/dev/bus/usb/001/006 187s ** (umockdev-run:3241): DEBUG: 05:38:32.459: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 187s ** (umockdev-run:3241): DEBUG: 05:38:32.462: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 187s ** (umockdev-run:3241): DEBUG: 05:38:32.467: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.P5QL22/dev/bus/usb/001/001 187s ** (umockdev-run:3241): DEBUG: 05:38:32.467: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 187s ** (umockdev-run:3241): DEBUG: 05:38:32.468: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 187s (process:3245): libfprint-context-DEBUG: 05:38:32.608: Initializing FpContext (libfprint version 1.94.9+tod1) 187s (process:3245): libfprint-tod-DEBUG: 05:38:32.609: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:3245): libfprint-context-DEBUG: 05:38:32.612: No driver found for USB device 1D6B:0002 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.613: 133453111: ../libfprint/drivers/realtek/realtek.c:1224 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.617: Device name: Realtek USB2.0 Finger Print Bridge 187s (process:3245): libfprint-device-DEBUG: 05:38:32.618: Device reported probe completion 187s (process:3245): libfprint-device-DEBUG: 05:38:32.618: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.618: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.620: 133459762: ../libfprint/drivers/realtek/realtek.c:1269 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.620: [realtek] Init entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.621: [realtek] Init entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.621: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.622: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.622: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.623: [realtek] Init entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.623: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.623: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.624: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.625: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.625: [realtek] Init completed successfully 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.625: Init complete! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.625: Device reported open completion 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.625: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.626: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.626: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.626: 133465632: ../libfprint/drivers/realtek/realtek.c:1332 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.626: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.626: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.626: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.628: Successfully cleared storage 187s (process:3245): libfprint-device-DEBUG: 05:38:32.628: Device reported deletion completion 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.628: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.628: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.628: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.629: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.629: 133469361: ../libfprint/drivers/realtek/realtek.c:1201 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.629: [realtek] Enroll entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.630: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.630: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.631: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.632: [realtek] Enroll entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.632: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.633: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.633: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.633: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.634: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.634: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.634: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.634: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.635: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.635: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.636: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.636: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.636: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.636: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.637: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.638: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.638: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.638: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.638: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.639: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.640: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.640: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.640: Device reported enroll progress, reported 1 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.641: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.641: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.641: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.641: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.641: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.641: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.642: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.642: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.643: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.643: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.644: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.645: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.645: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.645: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.645: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.645: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.646: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.647: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.647: Device reported enroll progress, reported 2 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.647: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.647: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.647: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.648: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.648: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.648: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.649: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.649: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.650: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.650: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.651: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.652: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.652: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.652: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.653: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.653: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.654: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.655: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.655: Device reported enroll progress, reported 3 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.655: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.655: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.655: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.656: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.656: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.657: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.657: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.657: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.658: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.658: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.659: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.659: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.659: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.660: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.660: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.661: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.662: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.662: Device reported enroll progress, reported 4 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.662: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.662: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.662: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.662: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.662: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.663: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.663: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.664: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.664: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.665: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.666: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.666: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.666: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.666: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.666: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.667: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.668: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.668: Device reported enroll progress, reported 5 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.668: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.668: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.668: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.669: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.669: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.669: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.670: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.670: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.670: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.671: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.672: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.673: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.673: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.673: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.673: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.674: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.675: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.676: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.676: Device reported enroll progress, reported 6 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.676: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.676: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.677: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.677: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.677: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.678: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.678: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.679: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.679: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.681: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.682: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.682: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.682: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.682: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.683: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.684: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.685: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.685: Device reported enroll progress, reported 7 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.685: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.685: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.685: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.685: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.685: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.686: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.686: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.686: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.687: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.687: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.689: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.689: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.689: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.689: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.690: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.691: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.691: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-device-DEBUG: 05:38:32.691: Device reported enroll progress, reported 8 of 8 have been completed 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.691: [realtek] Enroll entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.691: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.692: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.692: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.692: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.693: [realtek] Enroll entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.693: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.694: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.695: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.695: [realtek] Enroll entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.696: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.696: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.697: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.698: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.698: [realtek] Enroll entering state 5 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.698: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.699: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.699: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.700: [realtek] Enroll entering state 6 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.701: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.701: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.701: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.702: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.703: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.704: [realtek] Enroll completed successfully 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.704: Enrollment complete! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.704: Device reported enroll completion 187s (process:3245): libfprint-device-DEBUG: 05:38:32.704: Print for finger FP_FINGER_UNKNOWN enrolled 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.704: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.704: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.704: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.704: 133544217: ../libfprint/drivers/realtek/realtek.c:1344 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.704: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.705: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.706: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.707: Query templates complete! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.707: Device reported listing completion 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.707: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.707: Completing action FPI_DEVICE_ACTION_LIST in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.708: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.708: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.708: 133548043: ../libfprint/drivers/realtek/realtek.c:1177 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.708: [realtek] Verify & Identify entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.708: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.711: [realtek] Verify & Identify entering state 1 187s (process:3245): libfprint-device-DEBUG: 05:38:32.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.711: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.713: [realtek] Verify & Identify entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.713: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.715: [realtek] Verify & Identify entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.716: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.718: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.718: [realtek] Verify & Identify entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.718: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.720: Device reported verify result 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.720: [realtek] Verify & Identify entering state 5 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.725: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.726: [realtek] Verify & Identify completed successfully 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.726: Verify complete! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.726: Device reported verify completion 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.726: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.726: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.726: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.727: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.727: 133567356: ../libfprint/drivers/realtek/realtek.c:1177 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.727: [realtek] Verify & Identify entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.730: [realtek] Verify & Identify entering state 1 187s (process:3245): libfprint-device-DEBUG: 05:38:32.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.730: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.731: [realtek] Verify & Identify entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.732: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.734: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.734: [realtek] Verify & Identify entering state 3 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.734: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.736: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.736: [realtek] Verify & Identify entering state 4 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.736: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-device-DEBUG: 05:38:32.738: Device reported identify result 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.738: [realtek] Verify & Identify completed successfully 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.738: Verify complete! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.738: Device reported identify completion 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.738: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.738: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.738: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.739: 133578882: ../libfprint/drivers/realtek/realtek.c:1313 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.739: [realtek] Delete print entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.741: [realtek] Delete print entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.741: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.742: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.742: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.742: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.743: [realtek] Delete print completed successfully 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.743: Delete print complete! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.743: Device reported deletion completion 187s (process:3245): libfprint-SSM-DEBUG: 05:38:32.743: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 187s (process:3245): libfprint-device-DEBUG: 05:38:32.743: Completing action FPI_DEVICE_ACTION_DELETE in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.743: Not updating temperature model, device can run continuously! 187s (process:3245): libfprint-realtek-DEBUG: 05:38:32.744: 133583474: ../libfprint/drivers/realtek/realtek.c:1301 187s (process:3245): libfprint-device-DEBUG: 05:38:32.744: Device reported close completion 187s (process:3245): libfprint-device-DEBUG: 05:38:32.744: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:3245): libfprint-device-DEBUG: 05:38:32.744: Not updating temperature model, device can run continuously! 187s enrolling 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 1, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 2, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 3, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 4, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 5, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 6, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 7, None, None, None) 187s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79d69358a240 (FpiDeviceRealtek at 0x22abe120)>, 8, None, None, None) 187s enroll done 187s listing 187s listing done 187s verifying 187s verify done 187s async identifying 187s indentification_done: 187s deleting 187s delete done 187s ** (umockdev-run:3241): DEBUG: 05:38:32.767: umockdev.vala:154: Removing test bed /tmp/umockdev.P5QL22 187s (umockdev-run:3241): GLib-DEBUG: 05:38:32.777: unsetenv() is not thread-safe and should not be used after threads are created 187s PASS: libfprint-2/driver-realtek-5816.test 187s Running test: libfprint-2/driver-uru4000-msv2.test 187s ** (umockdev-run:3253): DEBUG: 05:38:32.845: umockdev.vala:127: Created udev test bed /tmp/umockdev.0WE712 187s ** (umockdev-run:3253): DEBUG: 05:38:32.845: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 187s ** (umockdev-run:3253): DEBUG: 05:38:32.848: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 187s ** (umockdev-run:3253): DEBUG: 05:38:32.852: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.0WE712/dev/bus/usb/001/047 187s ** (umockdev-run:3253): DEBUG: 05:38:32.853: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 187s ** (umockdev-run:3253): DEBUG: 05:38:32.855: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 187s ** (umockdev-run:3253): DEBUG: 05:38:32.859: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.0WE712/dev/bus/usb/001/001 187s ** (umockdev-run:3253): DEBUG: 05:38:32.859: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 187s ** (umockdev-run:3253): DEBUG: 05:38:32.860: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 187s (process:3257): libfprint-context-DEBUG: 05:38:32.970: Initializing FpContext (libfprint version 1.94.9+tod1) 187s (process:3257): libfprint-tod-DEBUG: 05:38:32.970: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:3257): libfprint-context-DEBUG: 05:38:32.974: No driver found for USB device 1D6B:0002 187s (process:3257): libfprint-device-DEBUG: 05:38:32.975: Device reported probe completion 187s (process:3257): libfprint-device-DEBUG: 05:38:32.975: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:3257): libfprint-device-DEBUG: 05:38:32.975: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3257): libfprint-image_device-DEBUG: 05:38:32.981: Image device open completed 188s (process:3257): libfprint-device-DEBUG: 05:38:32.981: Device reported open completion 188s (process:3257): libfprint-device-DEBUG: 05:38:32.981: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:3257): libfprint-device-DEBUG: 05:38:32.981: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3257): libfprint-device-DEBUG: 05:38:32.982: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3257): libfprint-image_device-DEBUG: 05:38:32.982: Activating image device 188s (process:3257): libfprint-image_device-DEBUG: 05:38:32.982: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.982: [uru4000] INIT_NUM_STATES entering state 0 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.982: read 1 regs at 7 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.983: reg value 3 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.983: [uru4000] INIT_NUM_STATES entering state 1 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.983: [uru4000] INIT_NUM_STATES entering state 3 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.983: set 83 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.984: [uru4000] INIT_NUM_STATES entering state 4 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.984: [uru4000] POWERUP_NUM_STATES entering state 0 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.984: [uru4000] POWERUP_NUM_STATES entering state 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.985: set 03 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.985: [uru4000] POWERUP_NUM_STATES entering state 2 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.985: read 1 regs at 7 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.986: reg value 83 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.986: [uru4000] POWERUP_NUM_STATES entering state 3 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.986: [uru4000] POWERUP_NUM_STATES entering state 4 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.996: [uru4000] POWERUP_NUM_STATES entering state 5 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.997: 133836729: ../libfprint/drivers/uru4000.c:326 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.999: [uru4000] POWERUP_NUM_STATES entering state 6 188s (process:3257): libfprint-SSM-DEBUG: 05:38:32.999: [uru4000] POWERUP_NUM_STATES entering state 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:32.999: set 03 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.000: [uru4000] POWERUP_NUM_STATES entering state 2 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.000: read 1 regs at 7 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.001: reg value 3 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.001: [uru4000] POWERUP_NUM_STATES entering state 3 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.001: [uru4000] POWERUP_NUM_STATES completed successfully 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.001: [uru4000] INIT_NUM_STATES entering state 5 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.002: recv irq type 56aa 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.002: late scanpwr interrupt 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.002: [uru4000] INIT_NUM_STATES entering state 6 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.002: [uru4000] INIT_NUM_STATES entering state 7 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.002: read 16 regs at f0 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.003: reg value 50 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.003: [uru4000] INIT_NUM_STATES entering state 8 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.003: Versions 0059 and 0034 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.003: [uru4000] INIT_NUM_STATES completed successfully 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.004: Image device activation completed 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.004: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.004: wait finger on 188s (process:3257): libfprint-device-DEBUG: 05:38:33.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.006: recv irq type 0101 188s (process:3257): libfprint-device-DEBUG: 05:38:33.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.006: Image device reported finger status: on 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.006: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.006: starting capture 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.006: Image encryption seed: 1374298404 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.006: [uru4000] IMAGING_NUM_STATES entering state 0 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.008: [uru4000] IMAGING_NUM_STATES entering state 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.008: hw header lines 289 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.008: dev2: 10849 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.008: image seems to be encrypted 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.009: [uru4000] IMAGING_NUM_STATES entering state 2 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.009: read 4 regs at 34 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: reg value 7b 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.010: [uru4000] IMAGING_NUM_STATES entering state 3 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: encryption id 05 -> key db896f5f 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 0 02 67 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: decoding 67 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 1 00 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: skipping 1 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 2 02 49 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: decoding 49 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 3 01 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: skipping 1 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 4 00 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: skipping 1 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 5 02 49 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: decoding 49 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 6 00 1 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: skipping 1 lines 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: 7 02 121 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.010: decoding 121 lines 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.011: [uru4000] IMAGING_NUM_STATES entering state 4 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.011: Image device captured an image 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.011: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 188s (process:3257): libfprint-device-DEBUG: 05:38:33.011: Device reported finger status change: FP_FINGER_STATUS_PRESENT 188s (process:3257): libfprint-SSM-DEBUG: 05:38:33.012: [uru4000] IMAGING_NUM_STATES completed successfully 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.012: await finger off 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.014: recv irq type 0200 188s (process:3257): libfprint-device-DEBUG: 05:38:33.014: Device reported finger status change: FP_FINGER_STATUS_NONE 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.014: Image device reported finger status: off 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.014: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.014: Deactivating image device 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.014: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.014: deactivating 188s (process:3257): libfprint-uru4000-DEBUG: 05:38:33.015: cancelled 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.015: Image device deactivation completed 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 188s (process:3257): libfprint-image-DEBUG: 05:38:33.058: Minutiae scan completed in 0.046150 secs 188s (process:3257): libfprint-device-DEBUG: 05:38:33.058: Device reported capture completion 188s (process:3257): libfprint-device-DEBUG: 05:38:33.058: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 188s (process:3257): libfprint-device-DEBUG: 05:38:33.058: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 188s (process:3257): libfprint-image_device-DEBUG: 05:38:33.059: Image device close completed 188s (process:3257): libfprint-device-DEBUG: 05:38:33.059: Device reported close completion 188s (process:3257): libfprint-device-DEBUG: 05:38:33.059: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:3257): libfprint-device-DEBUG: 05:38:33.059: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s Executing: libfprint-2/driver-uru4000-msv2.test 188s ** (umockdev-run:3253): DEBUG: 05:38:33.328: umockdev.vala:154: Removing test bed /tmp/umockdev.0WE712 188s (umockdev-run:3253): GLib-DEBUG: 05:38:33.333: unsetenv() is not thread-safe and should not be used after threads are created 188s Comparing PNGs /tmp/libfprint-umockdev-test-j9j2hzkk/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 188s PASS: libfprint-2/driver-uru4000-msv2.test 188s Running test: libfprint-2/virtual-device.test 188s (process:3264): libfprint-context-DEBUG: 05:38:33.496: Initializing FpContext (libfprint version 1.94.9+tod1) 188s (process:3264): libfprint-tod-DEBUG: 05:38:33.496: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 188s (process:3264): libfprint-context-DEBUG: 05:38:33.500: No driver found for USB device 1D6B:0003 188s (process:3264): libfprint-context-DEBUG: 05:38:33.500: No driver found for USB device 0627:0001 188s (process:3264): libfprint-context-DEBUG: 05:38:33.500: No driver found for USB device 0627:0001 188s (process:3264): libfprint-context-DEBUG: 05:38:33.500: No driver found for USB device 1D6B:0002 188s (process:3264): libfprint-context-DEBUG: 05:38:33.500: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-gc3mu_xu/virtual-device.socket 188s (process:3264): libfprint-context-DEBUG: 05:38:33.500: created 188s (process:3264): libfprint-device-DEBUG: 05:38:33.502: Device reported probe completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.502: Completing action FPI_DEVICE_ACTION_PROBE in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.502: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.503: 134342509: ../libfprint/drivers/virtual-device.c:387 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.503: 134342594: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:3264): libfprint-device-DEBUG: 05:38:33.503: Device reported open completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.503: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.503: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.504: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.504: Got instructions of length 16 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.504: Received command SET_KEEP_ALIVE 0 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.504: Keep alive toggled: 0 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.504: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.504: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.504: Received command SET_ENROLL_STAGES 5 188s (process:3264): libfprint-device-DEBUG: 05:38:33.504: Device reported close completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.504: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.504: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s ok 188s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.504: 134344436: ../libfprint/drivers/virtual-device.c:387 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.504: 134344461: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:3264): libfprint-device-DEBUG: 05:38:33.505: Device reported open completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.505: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.505: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.505: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.505: Got instructions of length 20 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.505: Received command SET_ENROLL_STAGES 20 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.505: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.505: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.505: Received command SET_ENROLL_STAGES 1 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.506: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.506: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.506: Received command SET_ENROLL_STAGES 0 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.508: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.508: Got instructions of length 16 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.508: Received command SET_KEEP_ALIVE 0 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.508: Keep alive toggled: 0 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.509: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.509: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.509: Received command SET_ENROLL_STAGES 5 188s (process:3264): libfprint-device-DEBUG: 05:38:33.509: Device reported close completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.509: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.509: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s ok 188s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.509: 134348979: ../libfprint/drivers/virtual-device.c:387 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.509: 134349002: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:3264): libfprint-device-DEBUG: 05:38:33.509: Device reported open completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.509: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.509: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.510: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.510: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.510: Received command SET_SCAN_TYPE press 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.510: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.510: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.510: Received command SET_SCAN_TYPE swipe 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.510: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.510: Got instructions of length 25 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.510: Received command SET_SCAN_TYPE eye-contact 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.511: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.511: Got instructions of length 16 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.511: Received command SET_KEEP_ALIVE 0 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.511: Keep alive toggled: 0 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.511: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.511: Got instructions of length 19 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.511: Received command SET_ENROLL_STAGES 5 188s (process:3264): libfprint-device-DEBUG: 05:38:33.511: Device reported close completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.511: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.511: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s ok 188s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.511: 134351141: ../libfprint/drivers/virtual-device.c:387 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.511: 134351165: ../libfprint/drivers/virtual-device-listener.c:153 188s (process:3264): libfprint-device-DEBUG: 05:38:33.511: Device reported open completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.511: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.511: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.511: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.512: Got instructions of length 9 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.512: Received command SLEEP 100 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.512: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.512: Got instructions of length 7 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.512: Received command ERROR 4 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.512: Processing command SLEEP 100 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.512: Sleeping 100ms 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.613: Sleeping completed 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.613: Processing command ERROR 4 188s (process:3264): libfprint-device-DEBUG: 05:38:33.613: Device reported close completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.613: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.613: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s ok 188s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.614: 134453597: ../libfprint/drivers/virtual-device.c:387 188s (process:3264): libfprint-device-DEBUG: 05:38:33.614: Device reported open completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.614: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.614: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.614: Got instructions of length 16 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.614: Received command SET_KEEP_ALIVE 1 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.614: Keep alive toggled: 1 188s (process:3264): libfprint-device-DEBUG: 05:38:33.614: Device reported close completion 188s (process:3264): libfprint-device-DEBUG: 05:38:33.614: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 188s (process:3264): libfprint-device-DEBUG: 05:38:33.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:33.615: Got a new connection! 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.615: Got instructions of length 9 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.615: Received command SLEEP 500 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.615: 134454852: ../libfprint/drivers/virtual-device.c:387 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.615: Processing command SLEEP 500 188s (process:3264): libfprint-virtual_device-DEBUG: 05:38:33.615: Sleeping 500ms 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.116: Sleeping completed 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.116: 134955595: ../libfprint/drivers/virtual-device.c:387 189s (process:3264): libfprint-device-DEBUG: 05:38:34.116: Device reported open completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.116: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.116: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.116: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.116: Got instructions of length 16 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.116: Received command SET_KEEP_ALIVE 0 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.116: Keep alive toggled: 0 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.116: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Got instructions of length 19 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Received command SET_ENROLL_STAGES 5 189s (process:3264): libfprint-device-DEBUG: 05:38:34.117: Device reported close completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.117: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.117: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 189s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: 134956818: ../libfprint/drivers/virtual-device.c:387 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.117: 134956829: ../libfprint/drivers/virtual-device-listener.c:153 189s (process:3264): libfprint-device-DEBUG: 05:38:34.117: Device reported open completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.117: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.117: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.117: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Got instructions of length 16 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Received command IGNORED_COMMAND 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.117: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Got instructions of length 9 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Received command SLEEP 500 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.117: Processing command IGNORED_COMMAND 189s (process:3264): libfprint-device-DEBUG: 05:38:34.118: Device reported close completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.118: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.118: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.118: 134957737: ../libfprint/drivers/virtual-device.c:387 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.118: Processing command SLEEP 500 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.118: Sleeping 500ms 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.618: Sleeping completed 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.619: 135458486: ../libfprint/drivers/virtual-device.c:387 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.619: 135458520: ../libfprint/drivers/virtual-device-listener.c:153 189s (process:3264): libfprint-device-DEBUG: 05:38:34.619: Device reported open completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.619: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.619: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.619: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.619: Got instructions of length 16 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.619: Received command SET_KEEP_ALIVE 0 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.619: Keep alive toggled: 0 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.619: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.620: Got instructions of length 19 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.620: Received command SET_ENROLL_STAGES 5 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Device reported close completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s ok 189s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.620: 135459865: ../libfprint/drivers/virtual-device.c:387 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.620: 135459894: ../libfprint/drivers/virtual-device-listener.c:153 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Device reported open completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.620: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.620: Got instructions of length 16 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.620: Received command SET_KEEP_ALIVE 1 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.620: Keep alive toggled: 1 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Device reported close completion 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:3264): libfprint-device-DEBUG: 05:38:34.620: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:34.621: Got a new connection! 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.621: Got instructions of length 9 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.621: Received command SLEEP 500 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.621: 135460716: ../libfprint/drivers/virtual-device.c:387 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.621: Processing command SLEEP 500 189s (process:3264): libfprint-virtual_device-DEBUG: 05:38:34.621: Sleeping 500ms 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.121: Sleeping completed 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.122: 135961508: ../libfprint/drivers/virtual-device.c:387 190s (process:3264): libfprint-device-DEBUG: 05:38:35.122: Device reported open completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.122: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.122: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.122: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.122: Got instructions of length 16 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.122: Received command SET_KEEP_ALIVE 0 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.122: Keep alive toggled: 0 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.122: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.123: Got instructions of length 19 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.123: Received command SET_ENROLL_STAGES 5 190s (process:3264): libfprint-device-DEBUG: 05:38:35.123: Device reported close completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.123: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.123: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 190s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.123: 135962942: ../libfprint/drivers/virtual-device.c:387 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.123: 135962969: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:3264): libfprint-device-DEBUG: 05:38:35.123: Device reported open completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.123: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.123: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.124: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.124: Got instructions of length 16 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.124: Received command SET_KEEP_ALIVE 0 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.124: Keep alive toggled: 0 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.124: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.124: Got instructions of length 19 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.124: Received command SET_ENROLL_STAGES 5 190s (process:3264): libfprint-device-DEBUG: 05:38:35.124: Device reported close completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.124: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.124: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 190s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.124: 135964325: ../libfprint/drivers/virtual-device.c:387 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.124: 135964356: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:3264): libfprint-device-DEBUG: 05:38:35.124: Device reported open completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.125: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.125: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.125: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.125: Got instructions of length 16 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.125: Received command SET_KEEP_ALIVE 0 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.125: Keep alive toggled: 0 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.125: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.125: Got instructions of length 19 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.125: Received command SET_ENROLL_STAGES 5 190s (process:3264): libfprint-device-DEBUG: 05:38:35.125: Device reported close completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.125: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.125: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s ok 190s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.126: 135965549: ../libfprint/drivers/virtual-device.c:387 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.126: 135965577: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:3264): libfprint-device-DEBUG: 05:38:35.126: Device reported open completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.126: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.126: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.126: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.126: Got instructions of length 10 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.126: Received command SLEEP 1500 190s (process:3264): libfprint-device-DEBUG: 05:38:35.126: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.127: Processing command SLEEP 1500 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.127: Sleeping 1500ms 190s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 190s self.assertFalse(self.dev.supports_identify()) 190s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 190s self.assertFalse(self.dev.supports_capture()) 190s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 190s self.assertFalse(self.dev.has_storage()) 190s (process:3264): libfprint-device-DEBUG: 05:38:35.426: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s (process:3264): libfprint-device-DEBUG: 05:38:35.427: Idle cancelling on ongoing operation! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.427: Got cancellation! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.427: Virtual device scan failed with error: Operation was cancelled 190s (process:3264): libfprint-device-DEBUG: 05:38:35.427: Device reported verify completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.427: Device reported finger status change: FP_FINGER_STATUS_NONE 190s (process:3264): libfprint-device-DEBUG: 05:38:35.427: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.427: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.627: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.627: Got instructions of length 16 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.627: Received command SET_KEEP_ALIVE 0 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.627: Keep alive toggled: 0 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.627: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.628: Got instructions of length 19 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.628: Received command SET_ENROLL_STAGES 5 190s (process:3264): libfprint-device-DEBUG: 05:38:35.628: Device reported close completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.628: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.628: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s ok 190s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.628: 136467955: ../libfprint/drivers/virtual-device.c:387 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.628: 136467979: ../libfprint/drivers/virtual-device-listener.c:153 190s (process:3264): libfprint-device-DEBUG: 05:38:35.628: Device reported open completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.628: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.628: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.629: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Got instructions of length 14 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Received command SCAN foo-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Processing command SCAN foo-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported enroll progress, reported 1 of 5 have been completed 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Sleeping completed 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.629: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Got instructions of length 14 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Received command SCAN foo-print 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.629: Processing command SCAN foo-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.629: Device reported enroll progress, reported 2 of 5 have been completed 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Sleeping completed 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.630: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Got instructions of length 14 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Received command SCAN foo-print 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Processing command SCAN foo-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:3264): libfprint-device-DEBUG: 05:38:35.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.630: Device reported enroll progress, reported 3 of 5 have been completed 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Sleeping completed 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.630: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Got instructions of length 14 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Received command SCAN foo-print 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Processing command SCAN foo-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:3264): libfprint-device-DEBUG: 05:38:35.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.630: Device reported enroll progress, reported 4 of 5 have been completed 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.630: Sleeping completed 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.630: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Got instructions of length 14 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Received command SCAN foo-print 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Processing command SCAN foo-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Device reported enroll progress, reported 5 of 5 have been completed 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Device reported enroll completion 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Device reported finger status change: FP_FINGER_STATUS_NONE 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Print for finger FP_FINGER_LEFT_RING enrolled 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.631: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Got instructions of length 9 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Received command SLEEP 100 190s (process:3264): libfprint-device-DEBUG: 05:38:35.631: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Processing command SLEEP 100 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.631: Sleeping 100ms 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.632: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.632: Got instructions of length 14 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.632: Received command SCAN bar-print 190s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:35.632: Got a new connection! 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.632: Got instructions of length 9 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.632: Received command SLEEP 800 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.731: Sleeping completed 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.732: Processing command SCAN bar-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-device-DEBUG: 05:38:35.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.732: Virtual device scanned print bar-print 190s (process:3264): libfprint-device-DEBUG: 05:38:35.732: Device reported verify result 190s (process:3264): libfprint-device-DEBUG: 05:38:35.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.732: Processing command SLEEP 800 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.732: Sleeping 800ms 190s (process:3264): libfprint-virtual_device-DEBUG: 05:38:35.732: Sleeping now, command queued for later: SCAN bar-print 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.533: Sleeping completed 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.533: Processing command SCAN bar-print 191s (process:3264): libfprint-device-DEBUG: 05:38:36.533: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.533: Virtual device scanned print bar-print 191s (process:3264): libfprint-device-DEBUG: 05:38:36.533: Device reported finger status change: FP_FINGER_STATUS_NEEDED 191s (process:3264): libfprint-device-DEBUG: 05:38:36.533: Device reported verify completion 191s (process:3264): libfprint-device-DEBUG: 05:38:36.533: Device reported finger status change: FP_FINGER_STATUS_NONE 191s (process:3264): libfprint-device-DEBUG: 05:38:36.533: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 191s (process:3264): libfprint-device-DEBUG: 05:38:36.533: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:36.533: Got a new connection! 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.534: Got instructions of length 16 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.534: Received command SET_KEEP_ALIVE 0 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.534: Keep alive toggled: 0 191s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:36.534: Got a new connection! 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.534: Got instructions of length 19 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.534: Received command SET_ENROLL_STAGES 5 191s (process:3264): libfprint-device-DEBUG: 05:38:36.534: Device reported close completion 191s (process:3264): libfprint-device-DEBUG: 05:38:36.534: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 191s (process:3264): libfprint-device-DEBUG: 05:38:36.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s Enroll done 191s ok 191s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.534: 137374153: ../libfprint/drivers/virtual-device.c:387 191s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:36.534: 137374180: ../libfprint/drivers/virtual-device-listener.c:153 191s (process:3264): libfprint-device-DEBUG: 05:38:36.534: Device reported open completion 191s (process:3264): libfprint-device-DEBUG: 05:38:36.534: Completing action FPI_DEVICE_ACTION_OPEN in idle! 191s (process:3264): libfprint-device-DEBUG: 05:38:36.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:36.535: Got a new connection! 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Got instructions of length 26 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Received command SET_CANCELLATION_ENABLED 0 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Cancellation support toggled: 0 191s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:36.535: Got a new connection! 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Got instructions of length 10 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Received command SLEEP 1500 191s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:36.535: Got a new connection! 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Got instructions of length 14 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Received command SCAN foo-print 191s (process:3264): libfprint-device-DEBUG: 05:38:36.535: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Processing command SLEEP 1500 191s (process:3264): libfprint-virtual_device-DEBUG: 05:38:36.535: Sleeping 1500ms 191s (process:3264): libfprint-device-DEBUG: 05:38:36.836: Idle cancelling on ongoing operation! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.036: Sleeping completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.037: Virtual device scan failed with error: Operation was cancelled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.037: Processing command SCAN foo-print 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.037: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.037: 138877427: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.037: 138877452: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.038: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.038: Device reported enroll progress, reported 1 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.038: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.038: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.039: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported enroll progress, reported 3 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.039: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.039: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.039: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.040: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Device reported enroll progress, reported 5 of 5 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Print for finger FP_FINGER_LEFT_LITTLE enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.040: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.040: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.040: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.040: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.041: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.041: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s Enroll done 193s ok 193s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: 138880630: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.041: 138880651: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.041: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.041: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.041: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.041: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: Received command SET_ENROLL_STAGES 8 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.041: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.041: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.041: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.042: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Received command RETRY 1 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.042: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.042: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Received command RETRY 3 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.042: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.042: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Received command RETRY 2 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.042: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.042: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.043: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Received command SLEEP 10 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.043: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Received command SLEEP 20 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.043: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Received command RETRY 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.043: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Received command RETRY 3 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.043: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.043: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.044: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Got instructions of length 15 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Received command SCAN another-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.044: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.044: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Received command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 1 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 2 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 2 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 3 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command RETRY 3 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 3 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 4 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command RETRY 2 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 4 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.044: Device reported enroll progress, reported 5 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Processing command SLEEP 10 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.044: Sleeping 10ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.055: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.055: Processing command SLEEP 20 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.055: Sleeping 20ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Processing command RETRY 0 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll progress, reported 5 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Processing command RETRY 3 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll progress, reported 5 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll progress, reported 6 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Processing command SCAN another-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll progress, reported 6 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll progress, reported 7 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.075: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll progress, reported 8 of 8 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.075: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.076: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.076: Print for finger FP_FINGER_UNKNOWN enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.076: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.076: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.076: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.076: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.076: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.076: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.076: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.076: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.076: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.077: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.077: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.077: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: 138916701: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.077: 138916724: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.077: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.077: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.077: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.077: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: Received command SLEEP 50 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.077: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.077: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.077: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.078: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Received command RETRY 1 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.078: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.078: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Received command SLEEP 50 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.078: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.078: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.078: Received command RETRY 2 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.078: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.079: Got instructions of length 15 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.079: Received command SCAN another-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.079: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.079: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.079: Received command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.079: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.079: Processing command SLEEP 50 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.079: Sleeping 50ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.129: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.129: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported enroll progress, reported 1 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.129: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.129: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.129: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.129: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.129: Processing command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.130: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.130: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.130: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.130: Device reported enroll progress, reported 3 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.130: Processing command SLEEP 50 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.130: Sleeping 50ms 193s Executing: libfprint-2/virtual-device.test 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Processing command RETRY 2 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Processing command SCAN another-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.180: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported enroll progress, reported 5 of 5 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Print for finger FP_FINGER_UNKNOWN enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.180: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.181: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.181: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.181: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.181: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.181: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.181: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.181: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.181: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.181: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.181: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.181: 139021401: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.181: 139021417: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.182: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported enroll progress, reported 1 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.182: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.182: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.182: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.182: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported enroll progress, reported 3 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.183: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.183: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.183: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported enroll progress, reported 5 of 5 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Print for finger FP_FINGER_LEFT_RING enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.183: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.184: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Received command ERROR 0 193s (process:3264): libfprint-device-DEBUG: 05:38:38.184: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Processing command ERROR 0 193s (process:3264): libfprint-device-DEBUG: 05:38:38.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Virtual device scan failed with error: An unspecified error occurred! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.184: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.184: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.184: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.184: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.184: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.184: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.185: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.185: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.185: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.185: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.185: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.185: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s Enroll done 193s ok 193s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.185: 139024909: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.185: 139024930: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.185: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.185: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.185: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.185: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.185: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.185: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported enroll progress, reported 1 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.186: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.186: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.186: Device reported enroll progress, reported 3 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.186: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.187: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.187: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.187: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported enroll progress, reported 5 of 5 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Print for finger FP_FINGER_LEFT_THUMB enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.187: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.188: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Virtual device scanned print testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.188: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.188: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.188: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.188: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s Enroll done 193s ok 193s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: 139028534: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.189: 139028546: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.189: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported enroll progress, reported 1 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.189: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.189: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.189: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.189: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported enroll progress, reported 3 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.190: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.190: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported enroll progress, reported 5 of 5 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Print for finger FP_FINGER_LEFT_RING enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.190: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.190: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.190: Got instructions of length 18 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Received command SCAN not-testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Processing command SCAN not-testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Virtual device scanned print not-testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.191: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.191: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s Enroll done 193s ok 193s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.191: 139031288: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.191: 139031302: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.192: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Received command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Processing command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Virtual device scan failed with error: The swipe was too short, please try again. 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.192: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.192: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.192: 139032407: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.192: 139032418: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.193: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.193: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.193: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.193: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Received command SET_ENROLL_STAGES 8 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.193: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.193: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.193: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Received command RETRY 1 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.193: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.193: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.193: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command RETRY 3 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.194: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.194: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command RETRY 2 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.194: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.194: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command SLEEP 10 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.194: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command SLEEP 20 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.194: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.194: Received command RETRY 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.195: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Received command RETRY 3 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.195: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.195: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Got instructions of length 15 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Received command SCAN another-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.195: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Received command SCAN print-id 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.195: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Received command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported enroll progress, reported 1 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.195: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.195: Device reported enroll progress, reported 2 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported enroll progress, reported 2 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported enroll progress, reported 3 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command RETRY 3 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported enroll progress, reported 3 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported enroll progress, reported 4 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command RETRY 2 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported enroll progress, reported 4 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.196: Device reported enroll progress, reported 5 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Processing command SLEEP 10 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.196: Sleeping 10ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.206: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.206: Processing command SLEEP 20 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.206: Sleeping 20ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.226: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.226: Processing command RETRY 0 193s (process:3264): libfprint-device-DEBUG: 05:38:38.226: Device reported enroll progress, reported 5 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.226: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.226: Processing command RETRY 3 193s (process:3264): libfprint-device-DEBUG: 05:38:38.226: Device reported enroll progress, reported 5 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.226: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.226: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.226: Device reported enroll progress, reported 6 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Processing command SCAN another-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported enroll progress, reported 6 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported enroll progress, reported 7 of 8 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported enroll progress, reported 8 of 8 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Print for finger FP_FINGER_UNKNOWN enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.227: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.227: Received command RETRY 2 193s (process:3264): libfprint-device-DEBUG: 05:38:38.227: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Processing command RETRY 2 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Virtual device scan failed with error: The finger was not centered properly, please try again. 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.228: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Received command SLEEP 50 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.228: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Received command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.228: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Processing command SLEEP 50 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.228: Sleeping 50ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.278: Sleeping completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.278: Processing command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.278: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.278: Virtual device scan failed with error: The swipe was too short, please try again. 193s (process:3264): libfprint-device-DEBUG: 05:38:38.278: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.278: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.278: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.278: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.278: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.279: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.279: Got instructions of length 15 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.279: Received command SCAN another-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.279: Processing command SCAN another-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.279: Virtual device scanned print another-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.279: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.280: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Got instructions of length 13 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Received command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Processing command SCAN print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Virtual device scanned print print-id 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported verify result 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.280: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.280: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.280: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.280: 139120451: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.280: 139120467: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.281: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported enroll progress, reported 1 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.281: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.281: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.281: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.282: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Received command RETRY 1 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Processing command RETRY 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported enroll progress, reported 2 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.282: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported enroll progress, reported 3 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.282: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.282: Device reported enroll progress, reported 4 of 5 have been completed 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.282: Sleeping completed 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.283: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Received command SCAN testprint 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Device reported enroll progress, reported 5 of 5 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Print for finger FP_FINGER_LEFT_LITTLE enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.283: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.283: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.283: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s Enroll done 193s ok 193s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: 139123542: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.284: 139123556: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.284: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Received command FINGER 1 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Processing command FINGER 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.284: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Received command FINGER 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Processing command FINGER 0 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Idle cancelling on ongoing operation! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Got cancellation! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.284: Virtual device scan failed with error: Operation was cancelled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.285: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.285: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: 139124905: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.285: 139124918: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.285: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Received command SLEEP 10 193s (process:3264): libfprint-device-DEBUG: 05:38:38.285: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Processing command SLEEP 10 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.285: Sleeping 10ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.295: Sleeping completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.296: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Received command FINGER 1 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Processing command FINGER 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.296: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Got instructions of length 8 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Received command FINGER 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Processing command FINGER 0 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Idle cancelling on ongoing operation! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Got cancellation! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.296: Virtual device scan failed with error: Operation was cancelled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Device reported verify completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.296: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.297: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.297: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.297: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.297: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.297: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.297: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.297: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.297: 139137147: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.297: 139137160: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.297: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.298: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.298: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.298: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.298: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.298: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: 139138074: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.298: 139138087: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.298: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.298: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.298: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.298: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.298: Received command IGNORED_COMMAND 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.298: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Received command ERROR 5 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Processing command IGNORED_COMMAND 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: 139138864: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Processing command ERROR 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: 139139014: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.299: 139139029: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.299: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Received command SET_KEEP_ALIVE 1 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.299: Keep alive toggled: 1 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.299: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.300: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Got instructions of length 7 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Received command ERROR 5 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: 139139584: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Processing command ERROR 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s ok 193s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: 139139715: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.300: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Received command SET_ENROLL_STAGES 1 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.300: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Got instructions of length 14 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Received command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.300: Processing command SCAN testprint 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported enroll progress, reported 1 of 1 have been completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported enroll completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Device reported finger status change: FP_FINGER_STATUS_NONE 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Print for finger FP_FINGER_LEFT_LITTLE enrolled 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.300: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.301: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.301: Got instructions of length 16 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.301: Received command SET_KEEP_ALIVE 0 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.301: Keep alive toggled: 0 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.301: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.301: Got instructions of length 19 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.301: Received command SET_ENROLL_STAGES 5 193s (process:3264): libfprint-device-DEBUG: 05:38:38.301: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.301: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.301: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 193s Enroll done 193s ok 193s (process:3264): libfprint-context-DEBUG: 05:38:38.302: Initializing FpContext (libfprint version 1.94.9+tod1) 193s (process:3264): libfprint-tod-DEBUG: 05:38:38.302: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 193s (process:3264): libfprint-context-DEBUG: 05:38:38.306: No driver found for USB device 1D6B:0003 193s (process:3264): libfprint-context-DEBUG: 05:38:38.306: No driver found for USB device 0627:0001 193s (process:3264): libfprint-context-DEBUG: 05:38:38.306: No driver found for USB device 0627:0001 193s (process:3264): libfprint-context-DEBUG: 05:38:38.306: No driver found for USB device 1D6B:0002 193s (process:3264): libfprint-context-DEBUG: 05:38:38.306: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-fa3mjam6/virtual-device.socket 193s (process:3264): libfprint-context-DEBUG: 05:38:38.306: created 193s (process:3264): libfprint-device-DEBUG: 05:38:38.308: Device reported probe completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.308: Completing action FPI_DEVICE_ACTION_PROBE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.308: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.308: 139148356: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.308: 139148371: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.309: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.309: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.309: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.309: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.309: Got instructions of length 9 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.309: Received command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.309: Processing command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.309: Sleeping 200ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.509: Sleeping completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.509: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.509: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.510: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s ok 193s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.510: 139349649: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.510: 139349662: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.510: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.510: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.510: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.510: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.510: Got instructions of length 9 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.510: Received command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.510: Processing command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.510: Sleeping 200ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.711: Sleeping completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.711: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.711: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.711: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s ok 193s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.711: 139551352: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.711: 139551385: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.712: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.712: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.712: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.712: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.712: Got instructions of length 9 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.712: Received command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.712: Processing command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.712: Sleeping 200ms 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.913: Sleeping completed 193s (process:3264): libfprint-device-DEBUG: 05:38:38.913: Device reported close completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.913: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s ok 193s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.913: 139753208: ../libfprint/drivers/virtual-device.c:387 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.913: 139753224: ../libfprint/drivers/virtual-device-listener.c:153 193s (process:3264): libfprint-device-DEBUG: 05:38:38.913: Device reported open completion 193s (process:3264): libfprint-device-DEBUG: 05:38:38.913: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s (process:3264): libfprint-device-DEBUG: 05:38:38.913: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:38.914: Got a new connection! 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.914: Got instructions of length 9 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.914: Received command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.914: Processing command SLEEP 200 193s (process:3264): libfprint-virtual_device-DEBUG: 05:38:38.914: Sleeping 200ms 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.114: Sleeping completed 194s (process:3264): libfprint-device-DEBUG: 05:38:39.114: Device reported close completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.114: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.114: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s ok 194s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.115: 139954589: ../libfprint/drivers/virtual-device.c:387 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.115: 139954606: ../libfprint/drivers/virtual-device-listener.c:153 194s (process:3264): libfprint-device-DEBUG: 05:38:39.115: Device reported open completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.115: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.115: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.115: Got a new connection! 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.115: Got instructions of length 9 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.115: Received command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.115: Processing command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.115: Sleeping 200ms 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.316: Sleeping completed 194s (process:3264): libfprint-device-DEBUG: 05:38:39.316: Device reported close completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.316: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.316: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s ok 194s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.316: 140156215: ../libfprint/drivers/virtual-device.c:387 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.316: 140156228: ../libfprint/drivers/virtual-device-listener.c:153 194s (process:3264): libfprint-device-DEBUG: 05:38:39.316: Device reported open completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.317: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.317: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.317: Got a new connection! 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.317: Got instructions of length 9 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.317: Received command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.317: Processing command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.317: Sleeping 200ms 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.517: Sleeping completed 194s (process:3264): libfprint-device-DEBUG: 05:38:39.517: Device reported close completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.517: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.518: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s ok 194s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: 140357673: ../libfprint/drivers/virtual-device.c:387 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.518: 140357689: ../libfprint/drivers/virtual-device-listener.c:153 194s (process:3264): libfprint-device-DEBUG: 05:38:39.518: Device reported open completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.518: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.518: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.518: Got a new connection! 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Got instructions of length 9 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Received command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Processing command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Sleeping 200ms 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.518: Got a new connection! 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Got instructions of length 16 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Received command SET_KEEP_ALIVE 1 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.518: Keep alive toggled: 1 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.719: Sleeping completed 194s (process:3264): libfprint-device-DEBUG: 05:38:39.719: Device reported close completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.719: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.719: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.719: Got a new connection! 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.719: Got instructions of length 9 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.719: Received command SLEEP 100 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.719: 140559330: ../libfprint/drivers/virtual-device.c:387 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.719: Processing command SLEEP 100 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.719: Sleeping 100ms 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.820: Sleeping completed 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.820: 140659645: ../libfprint/drivers/virtual-device.c:387 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Device reported open completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Device reported close completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s ok 194s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.820: 140660252: ../libfprint/drivers/virtual-device.c:387 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Device reported open completion 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s (process:3264): libfprint-device-DEBUG: 05:38:39.820: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:39.821: Got a new connection! 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.821: Got instructions of length 9 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.821: Received command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.821: Processing command SLEEP 200 194s (process:3264): libfprint-virtual_device-DEBUG: 05:38:39.821: Sleeping 200ms 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.021: Sleeping completed 195s (process:3264): libfprint-device-DEBUG: 05:38:40.021: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.021: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.021: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.022: 140861711: ../libfprint/drivers/virtual-device.c:752 195s (process:3264): libfprint-context-DEBUG: 05:38:40.022: Initializing FpContext (libfprint version 1.94.9+tod1) 195s (process:3264): libfprint-tod-DEBUG: 05:38:40.022: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 195s (process:3264): libfprint-context-DEBUG: 05:38:40.025: No driver found for USB device 1D6B:0003 195s (process:3264): libfprint-context-DEBUG: 05:38:40.025: No driver found for USB device 0627:0001 195s (process:3264): libfprint-context-DEBUG: 05:38:40.025: No driver found for USB device 0627:0001 195s (process:3264): libfprint-context-DEBUG: 05:38:40.025: No driver found for USB device 1D6B:0002 195s (process:3264): libfprint-context-DEBUG: 05:38:40.025: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-j44ea6r5/virtual-device.socket 195s (process:3264): libfprint-context-DEBUG: 05:38:40.026: created 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Device reported probe completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.027: 140867184: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.027: 140867199: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.027: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.028: 140867574: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.028: 140867587: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.028: 140867881: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.028: 140867894: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.028: 140868264: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.028: 140868276: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.028: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.029: 140868569: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.029: 140868582: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.029: 140868872: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.029: 140868885: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.029: 140869157: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.029: 140869168: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.029: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.030: 140869595: ../libfprint/drivers/virtual-device.c:752 195s (process:3264): libfprint-context-DEBUG: 05:38:40.030: Initializing FpContext (libfprint version 1.94.9+tod1) 195s (process:3264): libfprint-tod-DEBUG: 05:38:40.030: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: No driver found for USB device 1D6B:0003 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: No driver found for USB device 0627:0001 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: No driver found for USB device 0627:0001 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: No driver found for USB device 1D6B:0002 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-j44ea6r5/virtual-device.socket 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: created 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ozyge6tv/virtual-device-storage.socket 195s (process:3264): libfprint-context-DEBUG: 05:38:40.033: created 195s (process:3264): libfprint-device-DEBUG: 05:38:40.034: Device reported probe completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.034: Device reported probe completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.034: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.034: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-device-DEBUG: 05:38:40.034: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.034: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.035: 140874742: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.035: 140874761: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.035: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.035: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.035: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.035: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.035: Got instructions of length 5 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.035: Received command CONT 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.035: Processing command CONT 195s (process:3264): libfprint-device-DEBUG: 05:38:40.035: Device reported deletion completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.035: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.035: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.036: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Got instructions of length 16 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Received command SET_KEEP_ALIVE 0 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Keep alive toggled: 0 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.036: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Received command SET_ENROLL_STAGES 5 195s (process:3264): libfprint-device-DEBUG: 05:38:40.036: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.036: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.036: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: 140875898: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.036: 140875913: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.036: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.036: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.036: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.036: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Got instructions of length 20 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Received command SET_ENROLL_STAGES 20 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.036: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.036: Received command SET_ENROLL_STAGES 1 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.037: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Received command SET_ENROLL_STAGES 0 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.037: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Got instructions of length 5 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Received command CONT 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Processing command CONT 195s (process:3264): libfprint-device-DEBUG: 05:38:40.037: Device reported deletion completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.037: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.037: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.037: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Got instructions of length 16 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Received command SET_KEEP_ALIVE 0 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Keep alive toggled: 0 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.037: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.037: Received command SET_ENROLL_STAGES 5 195s (process:3264): libfprint-device-DEBUG: 05:38:40.037: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.038: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.038: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: 140877583: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.038: 140877591: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.038: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.038: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.038: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.038: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: Received command SET_SCAN_TYPE press 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.038: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: Received command SET_SCAN_TYPE swipe 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.038: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: Got instructions of length 25 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.038: Received command SET_SCAN_TYPE eye-contact 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.039: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Got instructions of length 5 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Received command CONT 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Processing command CONT 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Device reported deletion completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.039: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Got instructions of length 16 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Received command SET_KEEP_ALIVE 0 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Keep alive toggled: 0 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.039: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Got instructions of length 19 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Received command SET_ENROLL_STAGES 5 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Device reported close completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s ok 195s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: 140879185: ../libfprint/drivers/virtual-device.c:387 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.039: 140879202: ../libfprint/drivers/virtual-device-listener.c:153 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Device reported open completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.039: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.039: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.039: Got instructions of length 9 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.040: Received command INSERT p1 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.040: Processing command INSERT p1 195s (process:3264): libfprint-device-DEBUG: 05:38:40.540: Device reported listing completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.540: Completing action FPI_DEVICE_ACTION_LIST in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.540: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:40.541: Got a new connection! 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.541: Got instructions of length 5 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.541: Received command CONT 195s (process:3264): libfprint-virtual_device-DEBUG: 05:38:40.541: Processing command CONT 195s (process:3264): libfprint-device-DEBUG: 05:38:40.541: Device reported deletion completion 195s (process:3264): libfprint-device-DEBUG: 05:38:40.541: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 195s (process:3264): libfprint-device-DEBUG: 05:38:40.541: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-device-DEBUG: 05:38:41.042: Device reported listing completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.042: Completing action FPI_DEVICE_ACTION_LIST in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.042: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.042: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.042: Got instructions of length 5 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.042: Received command CONT 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.043: Processing command CONT 196s (process:3264): libfprint-device-DEBUG: 05:38:41.043: Device reported deletion completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.043: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.043: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.043: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.043: Got instructions of length 16 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.043: Received command SET_KEEP_ALIVE 0 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.043: Keep alive toggled: 0 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.043: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.043: Got instructions of length 19 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.043: Received command SET_ENROLL_STAGES 5 196s (process:3264): libfprint-device-DEBUG: 05:38:41.043: Device reported close completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.043: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.043: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s 196s ok 196s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.044: 141883511: ../libfprint/drivers/virtual-device.c:387 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.044: 141883537: ../libfprint/drivers/virtual-device-listener.c:153 196s (process:3264): libfprint-device-DEBUG: 05:38:41.044: Device reported open completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.044: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.044: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.044: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.044: Got instructions of length 9 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.044: Received command INSERT p1 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.044: Processing command INSERT p1 196s (process:3264): libfprint-device-DEBUG: 05:38:41.545: Device reported listing completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.545: Completing action FPI_DEVICE_ACTION_LIST in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.545: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.545: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Got instructions of length 7 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Received command ERROR 5 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Processing command ERROR 5 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Device reported deletion completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.546: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Got instructions of length 5 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Received command CONT 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Processing command CONT 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Device reported deletion completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.546: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Got instructions of length 16 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Received command SET_KEEP_ALIVE 0 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Keep alive toggled: 0 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.546: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Got instructions of length 19 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.546: Received command SET_ENROLL_STAGES 5 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Device reported close completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.546: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s 196s ok 196s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: 142386498: ../libfprint/drivers/virtual-device.c:387 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.547: 142386509: ../libfprint/drivers/virtual-device-listener.c:153 196s (process:3264): libfprint-device-DEBUG: 05:38:41.547: Device reported open completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.547: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.547: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.547: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: Got instructions of length 9 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: Received command SLEEP 100 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.547: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: Got instructions of length 7 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: Received command ERROR 4 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: Processing command SLEEP 100 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.547: Sleeping 100ms 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.647: Sleeping completed 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.648: Processing command ERROR 4 196s (process:3264): libfprint-device-DEBUG: 05:38:41.648: Device reported close completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.648: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.648: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 196s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.649: 142488766: ../libfprint/drivers/virtual-device.c:387 196s (process:3264): libfprint-device-DEBUG: 05:38:41.649: Device reported open completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.649: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.649: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.649: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.650: Got instructions of length 16 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.650: Received command SET_KEEP_ALIVE 1 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.650: Keep alive toggled: 1 196s (process:3264): libfprint-device-DEBUG: 05:38:41.650: Device reported close completion 196s (process:3264): libfprint-device-DEBUG: 05:38:41.650: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s (process:3264): libfprint-device-DEBUG: 05:38:41.650: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:41.650: Got a new connection! 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.650: Got instructions of length 9 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.650: Received command SLEEP 500 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.651: 142490542: ../libfprint/drivers/virtual-device.c:387 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.651: Processing command SLEEP 500 196s (process:3264): libfprint-virtual_device-DEBUG: 05:38:41.651: Sleeping 500ms 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.151: Sleeping completed 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.152: 142991510: ../libfprint/drivers/virtual-device.c:387 197s (process:3264): libfprint-device-DEBUG: 05:38:42.152: Device reported open completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.152: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.152: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.152: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.153: Got instructions of length 5 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.153: Received command CONT 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.153: Processing command CONT 197s (process:3264): libfprint-device-DEBUG: 05:38:42.153: Device reported deletion completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.153: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.153: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.153: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.153: Got instructions of length 16 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.153: Received command SET_KEEP_ALIVE 0 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.153: Keep alive toggled: 0 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.154: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.154: Got instructions of length 19 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.154: Received command SET_ENROLL_STAGES 5 197s (process:3264): libfprint-device-DEBUG: 05:38:42.154: Device reported close completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.154: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.154: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 197s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.154: 142994154: ../libfprint/drivers/virtual-device.c:387 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.154: 142994197: ../libfprint/drivers/virtual-device-listener.c:153 197s (process:3264): libfprint-device-DEBUG: 05:38:42.154: Device reported open completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.155: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.155: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.155: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.155: Got instructions of length 16 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.155: Received command IGNORED_COMMAND 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.155: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.155: Got instructions of length 9 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.155: Received command SLEEP 500 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.156: Processing command IGNORED_COMMAND 197s (process:3264): libfprint-device-DEBUG: 05:38:42.156: Device reported close completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.156: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.156: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.156: 142996131: ../libfprint/drivers/virtual-device.c:387 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.156: Processing command SLEEP 500 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.156: Sleeping 500ms 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.657: Sleeping completed 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.657: 143496984: ../libfprint/drivers/virtual-device.c:387 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.657: 143497022: ../libfprint/drivers/virtual-device-listener.c:153 197s (process:3264): libfprint-device-DEBUG: 05:38:42.657: Device reported open completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.657: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.658: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.658: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.658: Got instructions of length 5 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.658: Received command CONT 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.658: Processing command CONT 197s (process:3264): libfprint-device-DEBUG: 05:38:42.658: Device reported deletion completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.658: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.658: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.658: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.658: Got instructions of length 16 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.658: Received command SET_KEEP_ALIVE 0 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.658: Keep alive toggled: 0 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.659: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.659: Got instructions of length 19 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.659: Received command SET_ENROLL_STAGES 5 197s (process:3264): libfprint-device-DEBUG: 05:38:42.659: Device reported close completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.659: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.659: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s ok 197s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.659: 143499034: ../libfprint/drivers/virtual-device.c:387 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.659: 143499054: ../libfprint/drivers/virtual-device-listener.c:153 197s (process:3264): libfprint-device-DEBUG: 05:38:42.659: Device reported open completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.659: Completing action FPI_DEVICE_ACTION_OPEN in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.659: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.659: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.659: Got instructions of length 16 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.659: Received command SET_KEEP_ALIVE 1 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.660: Keep alive toggled: 1 197s (process:3264): libfprint-device-DEBUG: 05:38:42.660: Device reported close completion 197s (process:3264): libfprint-device-DEBUG: 05:38:42.660: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:3264): libfprint-device-DEBUG: 05:38:42.660: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 197s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:42.660: Got a new connection! 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.660: Got instructions of length 9 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.660: Received command SLEEP 500 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.660: 143499872: ../libfprint/drivers/virtual-device.c:387 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.660: Processing command SLEEP 500 197s (process:3264): libfprint-virtual_device-DEBUG: 05:38:42.660: Sleeping 500ms 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.161: Sleeping completed 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.161: 144000786: ../libfprint/drivers/virtual-device.c:387 198s (process:3264): libfprint-device-DEBUG: 05:38:43.161: Device reported open completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.161: Completing action FPI_DEVICE_ACTION_OPEN in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.161: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.162: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.162: Got instructions of length 5 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.162: Received command CONT 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.162: Processing command CONT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.162: Device reported deletion completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.162: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.163: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.163: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.163: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.163: Received command SET_KEEP_ALIVE 0 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.163: Keep alive toggled: 0 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.163: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.163: Got instructions of length 19 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.163: Received command SET_ENROLL_STAGES 5 198s (process:3264): libfprint-device-DEBUG: 05:38:43.164: Device reported close completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.164: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.164: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s ok 198s Executing: libfprint-2/virtual-device.test 198s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.165: 144004493: ../libfprint/drivers/virtual-device.c:387 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.165: 144004555: ../libfprint/drivers/virtual-device-listener.c:153 198s (process:3264): libfprint-device-DEBUG: 05:38:43.165: Device reported open completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.165: Completing action FPI_DEVICE_ACTION_OPEN in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.165: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.166: Got instructions of length 9 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.166: Received command SLEEP 100 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.166: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.166: Got instructions of length 7 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.166: Received command ERROR 7 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.166: Processing command SLEEP 100 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.166: Sleeping 100ms 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.267: Sleeping completed 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.267: Processing command ERROR 7 198s (process:3264): libfprint-device-DEBUG: 05:38:43.267: Device reported deletion completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.267: Completing action FPI_DEVICE_ACTION_DELETE in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.267: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.268: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.268: Got instructions of length 5 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.268: Received command CONT 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.268: Processing command CONT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.268: Device reported deletion completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.268: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.268: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.269: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.269: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.269: Received command SET_KEEP_ALIVE 0 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.269: Keep alive toggled: 0 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.269: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.270: Got instructions of length 19 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.270: Received command SET_ENROLL_STAGES 5 198s (process:3264): libfprint-device-DEBUG: 05:38:43.270: Device reported close completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.270: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.270: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s ok 198s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.270: 144110200: ../libfprint/drivers/virtual-device.c:387 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.270: 144110261: ../libfprint/drivers/virtual-device-listener.c:153 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Device reported open completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Completing action FPI_DEVICE_ACTION_OPEN in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.271: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.271: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.271: Received command SCAN right-thumb 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.271: Processing command SCAN right-thumb 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:3264): libfprint-device-DEBUG: 05:38:43.271: Device reported enroll progress, reported 1 of 5 have been completed 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.272: Sleeping completed 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.272: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.272: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.272: Received command SCAN right-thumb 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.272: Processing command SCAN right-thumb 198s (process:3264): libfprint-device-DEBUG: 05:38:43.272: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.272: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:3264): libfprint-device-DEBUG: 05:38:43.272: Device reported enroll progress, reported 2 of 5 have been completed 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.272: Sleeping completed 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.273: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.273: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.273: Received command SCAN right-thumb 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.273: Processing command SCAN right-thumb 198s (process:3264): libfprint-device-DEBUG: 05:38:43.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:3264): libfprint-device-DEBUG: 05:38:43.273: Device reported enroll progress, reported 3 of 5 have been completed 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.273: Sleeping completed 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.274: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Received command SCAN right-thumb 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Processing command SCAN right-thumb 198s (process:3264): libfprint-device-DEBUG: 05:38:43.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:3264): libfprint-device-DEBUG: 05:38:43.274: Device reported enroll progress, reported 4 of 5 have been completed 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Sleeping completed 198s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:43.274: Got a new connection! 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Got instructions of length 16 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Received command SCAN right-thumb 198s (process:3264): libfprint-virtual_device-DEBUG: 05:38:43.274: Processing command SCAN right-thumb 198s (process:3264): libfprint-device-DEBUG: 05:38:43.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 198s (process:3264): libfprint-device-DEBUG: 05:38:43.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 198s (process:3264): libfprint-device-DEBUG: 05:38:43.275: Device reported enroll progress, reported 5 of 5 have been completed 198s (process:3264): libfprint-device-DEBUG: 05:38:43.275: Device reported enroll completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.275: Device reported finger status change: FP_FINGER_STATUS_NONE 198s (process:3264): libfprint-device-DEBUG: 05:38:43.275: Print for finger FP_FINGER_RIGHT_THUMB enrolled 198s (process:3264): libfprint-device-DEBUG: 05:38:43.275: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.275: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:43.776: Deleting print right-thumb for user testuser 198s (process:3264): libfprint-device-DEBUG: 05:38:43.776: Device reported deletion completion 198s (process:3264): libfprint-device-DEBUG: 05:38:43.776: Completing action FPI_DEVICE_ACTION_DELETE in idle! 198s (process:3264): libfprint-device-DEBUG: 05:38:43.776: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:44.277: Deleting print right-thumb for user testuser 199s (process:3264): libfprint-device-DEBUG: 05:38:44.277: Device reported deletion completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.277: Completing action FPI_DEVICE_ACTION_DELETE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.277: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.278: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Got instructions of length 5 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Received command CONT 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Processing command CONT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.278: Device reported deletion completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.278: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.278: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.278: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Got instructions of length 16 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Received command SET_KEEP_ALIVE 0 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Keep alive toggled: 0 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.278: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Got instructions of length 19 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.278: Received command SET_ENROLL_STAGES 5 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Device reported close completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s Enroll done 199s ok 199s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: 145118651: ../libfprint/drivers/virtual-device.c:387 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.279: 145118663: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Device reported open completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.279: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Got instructions of length 5 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Received command CONT 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Processing command CONT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Device reported deletion completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.279: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Got instructions of length 16 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Received command SET_KEEP_ALIVE 0 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Keep alive toggled: 0 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.279: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Got instructions of length 19 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: Received command SET_ENROLL_STAGES 5 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Device reported close completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.279: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 199s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.279: 145119457: ../libfprint/drivers/virtual-device.c:387 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.279: 145119465: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:3264): libfprint-device-DEBUG: 05:38:44.280: Device reported open completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.280: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.280: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.280: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.280: Got instructions of length 5 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.280: Received command CONT 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.280: Processing command CONT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.280: Device reported deletion completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.280: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.280: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.280: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.280: Got instructions of length 16 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.280: Received command SET_KEEP_ALIVE 0 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.280: Keep alive toggled: 0 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.280: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.281: Got instructions of length 19 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.281: Received command SET_ENROLL_STAGES 5 199s (process:3264): libfprint-device-DEBUG: 05:38:44.281: Device reported close completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.281: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.281: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 199s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.281: 145120985: ../libfprint/drivers/virtual-device.c:387 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.281: 145121014: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:3264): libfprint-device-DEBUG: 05:38:44.281: Device reported open completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.281: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.281: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.281: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.281: Got instructions of length 10 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.281: Received command SLEEP 1500 199s (process:3264): libfprint-device-DEBUG: 05:38:44.282: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.282: Processing command SLEEP 1500 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.282: Sleeping 1500ms 199s (process:3264): libfprint-device-DEBUG: 05:38:44.582: Idle cancelling on ongoing operation! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.582: Got cancellation! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.582: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.582: Device reported identify completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.582: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:3264): libfprint-device-DEBUG: 05:38:44.582: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.582: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.782: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Got instructions of length 5 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Received command CONT 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Processing command CONT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.783: Device reported deletion completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.783: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.783: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.783: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Got instructions of length 16 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Received command SET_KEEP_ALIVE 0 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Keep alive toggled: 0 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.783: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Got instructions of length 19 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.783: Received command SET_ENROLL_STAGES 5 199s (process:3264): libfprint-device-DEBUG: 05:38:44.783: Device reported close completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.783: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.783: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 199s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: 145623534: ../libfprint/drivers/virtual-device.c:387 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.784: 145623559: ../libfprint/drivers/virtual-device-listener.c:153 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Device reported open completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.784: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Got instructions of length 14 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Received command SCAN foo-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Processing command SCAN foo-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.784: Device reported enroll progress, reported 1 of 5 have been completed 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Sleeping completed 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.784: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Got instructions of length 14 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Received command SCAN foo-print 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.784: Processing command SCAN foo-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported enroll progress, reported 2 of 5 have been completed 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Sleeping completed 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.785: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Got instructions of length 14 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Received command SCAN foo-print 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Processing command SCAN foo-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported enroll progress, reported 3 of 5 have been completed 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Sleeping completed 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.785: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Got instructions of length 14 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Received command SCAN foo-print 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Processing command SCAN foo-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.785: Device reported enroll progress, reported 4 of 5 have been completed 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.785: Sleeping completed 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.786: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Got instructions of length 14 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Received command SCAN foo-print 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Processing command SCAN foo-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Device reported enroll progress, reported 5 of 5 have been completed 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Device reported enroll completion 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Print for finger FP_FINGER_LEFT_RING enrolled 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.786: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Got instructions of length 9 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Received command SLEEP 100 199s (process:3264): libfprint-device-DEBUG: 05:38:44.786: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Processing command SLEEP 100 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.786: Sleeping 100ms 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.786: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.787: Got instructions of length 14 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.787: Received command SCAN bar-print 199s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:44.787: Got a new connection! 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.787: Got instructions of length 9 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.787: Received command SLEEP 800 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.886: Sleeping completed 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.887: Processing command SCAN bar-print 199s (process:3264): libfprint-device-DEBUG: 05:38:44.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-device-DEBUG: 05:38:44.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:44.887: Trying to identify print 'bar-print' against a gallery of 1 prints 199s (process:3264): libfprint-device-DEBUG: 05:38:44.887: Device reported identify result 199s (process:3264): libfprint-device-DEBUG: 05:38:44.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.887: Processing command SLEEP 800 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.887: Sleeping 800ms 199s (process:3264): libfprint-virtual_device-DEBUG: 05:38:44.887: Sleeping now, command queued for later: SCAN bar-print 200s (process:3264): libfprint-device-DEBUG: 05:38:45.123: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.688: Sleeping completed 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.688: Processing command SCAN bar-print 200s (process:3264): libfprint-device-DEBUG: 05:38:45.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 200s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:45.688: Trying to identify print 'bar-print' against a gallery of 1 prints 200s (process:3264): libfprint-device-DEBUG: 05:38:45.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED 200s (process:3264): libfprint-device-DEBUG: 05:38:45.688: Device reported identify completion 200s (process:3264): libfprint-device-DEBUG: 05:38:45.688: Device reported finger status change: FP_FINGER_STATUS_NONE 200s (process:3264): libfprint-device-DEBUG: 05:38:45.688: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 200s (process:3264): libfprint-device-DEBUG: 05:38:45.688: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.689: Got a new connection! 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.689: Got instructions of length 5 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.689: Received command CONT 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.689: Processing command CONT 200s (process:3264): libfprint-device-DEBUG: 05:38:45.689: Device reported deletion completion 200s (process:3264): libfprint-device-DEBUG: 05:38:45.689: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 200s (process:3264): libfprint-device-DEBUG: 05:38:45.689: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.689: Got a new connection! 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.690: Got instructions of length 16 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.690: Received command SET_KEEP_ALIVE 0 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.690: Keep alive toggled: 0 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.690: Got a new connection! 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.690: Got instructions of length 19 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.690: Received command SET_ENROLL_STAGES 5 200s (process:3264): libfprint-device-DEBUG: 05:38:45.690: Device reported close completion 200s (process:3264): libfprint-device-DEBUG: 05:38:45.690: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:3264): libfprint-device-DEBUG: 05:38:45.690: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 200s Enroll done 200s ok 200s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.690: 146530463: ../libfprint/drivers/virtual-device.c:387 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.691: 146530498: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:3264): libfprint-device-DEBUG: 05:38:45.691: Device reported open completion 200s (process:3264): libfprint-device-DEBUG: 05:38:45.691: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:3264): libfprint-device-DEBUG: 05:38:45.691: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.691: Got a new connection! 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.691: Got instructions of length 26 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.691: Received command SET_CANCELLATION_ENABLED 0 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.691: Cancellation support toggled: 0 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.691: Got a new connection! 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.691: Got instructions of length 10 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.691: Received command SLEEP 1500 200s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:45.692: Got a new connection! 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.692: Got instructions of length 14 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.692: Received command SCAN foo-print 200s (process:3264): libfprint-device-DEBUG: 05:38:45.692: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.692: Processing command SLEEP 1500 200s (process:3264): libfprint-virtual_device-DEBUG: 05:38:45.692: Sleeping 1500ms 201s (process:3264): libfprint-device-DEBUG: 05:38:45.992: Idle cancelling on ongoing operation! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.193: Sleeping completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.193: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.193: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.194: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.194: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.194: Processing command SCAN foo-print 202s (process:3264): libfprint-device-DEBUG: 05:38:47.194: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.194: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.194: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.195: 148035027: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.195: 148035084: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.195: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.195: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.196: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.196: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.196: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.196: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.196: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.196: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.196: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.197: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.197: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.197: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.197: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.197: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.197: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.197: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.197: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.198: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.198: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.198: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.198: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.199: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.199: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.199: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.199: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.199: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Print for finger FP_FINGER_LEFT_LITTLE enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.199: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.200: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.200: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.200: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.200: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.201: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.201: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.201: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.201: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.202: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.202: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.202: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.202: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.202: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.202: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s Enroll done 202s ok 202s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.202: 148042109: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.202: 148042136: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.202: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.202: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.202: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.203: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.203: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.203: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.203: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.204: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.204: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.204: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.204: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.204: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.204: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.204: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.204: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.205: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.205: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Print for finger FP_FINGER_LEFT_LITTLE enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.205: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.206: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.206: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.206: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.206: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.206: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.206: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.206: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.206: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.206: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.206: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.206: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.206: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.207: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.207: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.207: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.207: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.207: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s ok 202s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.207: 148046996: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.207: 148047021: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.207: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.207: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.207: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.208: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.208: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.208: Received command SET_ENROLL_STAGES 8 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.208: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.208: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.208: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.208: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.208: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.208: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.209: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.209: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.209: Received command RETRY 1 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.209: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.209: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.209: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.210: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.210: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.210: Received command RETRY 3 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.210: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.210: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.210: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.210: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.210: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.210: Received command RETRY 2 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.211: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.211: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.211: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.211: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.211: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.211: Received command SLEEP 10 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.211: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.212: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.212: Received command SLEEP 20 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.212: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.212: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.212: Received command RETRY 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.212: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.212: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.212: Received command RETRY 3 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.212: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.213: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Received command SCAN another-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.213: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.213: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.213: Received command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 1 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 2 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 2 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 3 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command RETRY 3 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 3 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 4 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command RETRY 2 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 4 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.214: Device reported enroll progress, reported 5 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Processing command SLEEP 10 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.214: Sleeping 10ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.224: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.225: Processing command SLEEP 20 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.225: Sleeping 20ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.245: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.245: Processing command RETRY 0 202s (process:3264): libfprint-device-DEBUG: 05:38:47.245: Device reported enroll progress, reported 5 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.245: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.245: Processing command RETRY 3 202s (process:3264): libfprint-device-DEBUG: 05:38:47.245: Device reported enroll progress, reported 5 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.245: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.245: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported enroll progress, reported 6 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.246: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.246: Processing command SCAN another-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported enroll progress, reported 6 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.246: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.246: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported enroll progress, reported 7 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.246: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.246: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported enroll progress, reported 8 of 8 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Print for finger FP_FINGER_UNKNOWN enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.246: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.247: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.247: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.247: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.247: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.248: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.248: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.248: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.248: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.248: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.248: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.248: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.248: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.248: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.249: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.249: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.249: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.249: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.249: 148089044: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.249: 148089085: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.249: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.249: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.249: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.250: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.250: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.250: Received command SLEEP 50 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.250: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.250: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.250: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.250: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.250: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.251: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.251: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.251: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.251: Received command RETRY 1 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.251: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.251: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.251: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.251: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.252: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.252: Received command SLEEP 50 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.252: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.252: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.252: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.252: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.252: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.252: Received command RETRY 2 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.253: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.253: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.253: Received command SCAN another-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.253: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.253: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.253: Received command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.253: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.253: Processing command SLEEP 50 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.253: Sleeping 50ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.304: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.304: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.304: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.304: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.304: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.304: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.304: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.305: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.305: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.305: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.305: Processing command SLEEP 50 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.305: Sleeping 50ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.355: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.355: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.355: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.356: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.356: Processing command RETRY 2 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.356: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.356: Processing command SCAN another-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.356: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.356: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.356: Print for finger FP_FINGER_UNKNOWN enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.357: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.357: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.357: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.357: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.358: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.358: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.358: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.358: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.358: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.358: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.358: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.358: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.358: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.359: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.359: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.359: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.359: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.359: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.359: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.359: 148199220: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.359: 148199260: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.359: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.360: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.360: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.360: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.360: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.360: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.360: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.361: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.361: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.361: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.361: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.361: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.361: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.361: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.361: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.361: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.362: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.362: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.362: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Print for finger FP_FINGER_LEFT_RING enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.362: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.363: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.363: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.363: Received command ERROR 0 202s (process:3264): libfprint-device-DEBUG: 05:38:47.363: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.363: Processing command ERROR 0 202s (process:3264): libfprint-device-DEBUG: 05:38:47.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.363: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.363: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.363: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.363: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.363: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.363: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.363: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.364: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.364: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.364: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.364: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.364: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.364: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.364: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.364: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.364: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.364: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.364: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.364: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.364: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.364: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s ok 202s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.365: 148204504: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.365: 148204525: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.365: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.365: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.365: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.365: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.365: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.365: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.366: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.366: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.366: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.366: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.366: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.366: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.366: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.366: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.366: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.367: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.367: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.367: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Print for finger FP_FINGER_LEFT_THUMB enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.367: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.368: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.368: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.368: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.368: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.368: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.368: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.369: Trying to identify print 'testprint' against a gallery of 1 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.369: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.369: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.369: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.369: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.369: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.369: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.369: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.369: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.369: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.370: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.370: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.370: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.370: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.370: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s ok 202s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.370: 148210100: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.370: 148210124: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.370: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.370: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.371: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.371: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.371: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.371: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.372: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.372: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.372: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.372: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.372: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.372: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.372: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.372: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.372: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.373: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.373: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.373: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.373: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Print for finger FP_FINGER_LEFT_RING enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.373: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.373: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.374: Got instructions of length 18 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.374: Received command SCAN not-testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.374: Processing command SCAN not-testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.374: Trying to identify print 'not-testprint' against a gallery of 1 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.374: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.374: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.374: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.374: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.374: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.374: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.375: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.375: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.375: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.375: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.375: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.375: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.375: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.375: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.375: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s ok 202s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.375: 148215187: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.375: 148215207: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.375: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.375: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.375: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.376: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.376: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.376: Received command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.376: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.376: Virtual device scan failed with error: The swipe was too short, please try again. 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Device reported verify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Device reported verify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.376: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.376: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.376: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.376: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.377: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.377: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.377: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.377: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.377: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.377: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.377: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.377: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.377: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.377: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.377: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.377: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.377: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.377: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.378: 148217491: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.378: 148217510: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.378: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.378: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.378: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.378: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.378: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.378: Received command SET_ENROLL_STAGES 8 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.378: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.378: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.378: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.379: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.379: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.379: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.379: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.379: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.379: Received command RETRY 1 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.379: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.379: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.379: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.379: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.380: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.380: Received command RETRY 3 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.380: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.380: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.380: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.380: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.380: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.380: Received command RETRY 2 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.381: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.381: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.381: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.381: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.381: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.381: Received command SLEEP 10 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.381: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.382: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.382: Received command SLEEP 20 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.382: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.382: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.382: Received command RETRY 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.382: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.382: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.382: Received command RETRY 3 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.382: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.383: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.383: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.383: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.383: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.383: Received command SCAN another-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.383: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.383: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.383: Received command SCAN print-id 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.383: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Received command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported enroll progress, reported 1 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported enroll progress, reported 2 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported enroll progress, reported 2 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.384: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.384: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported enroll progress, reported 3 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Processing command RETRY 3 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported enroll progress, reported 3 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported enroll progress, reported 4 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Processing command RETRY 2 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported enroll progress, reported 4 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.385: Device reported enroll progress, reported 5 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Processing command SLEEP 10 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.385: Sleeping 10ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.395: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.396: Processing command SLEEP 20 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.396: Sleeping 20ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.416: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.416: Processing command RETRY 0 202s (process:3264): libfprint-device-DEBUG: 05:38:47.416: Device reported enroll progress, reported 5 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.416: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.416: Processing command RETRY 3 202s (process:3264): libfprint-device-DEBUG: 05:38:47.416: Device reported enroll progress, reported 5 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported enroll progress, reported 6 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Processing command SCAN another-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported enroll progress, reported 6 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported enroll progress, reported 7 of 8 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.417: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported enroll progress, reported 8 of 8 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Print for finger FP_FINGER_UNKNOWN enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.417: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.418: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.418: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.418: Received command RETRY 2 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.419: Processing command RETRY 2 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.419: Virtual device scan failed with error: The finger was not centered properly, please try again. 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Device reported verify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Device reported verify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.419: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.419: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.419: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.419: Received command SLEEP 50 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.419: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.419: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.420: Received command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.420: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.420: Processing command SLEEP 50 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.420: Sleeping 50ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.470: Sleeping completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.470: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.470: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.470: Virtual device scan failed with error: The swipe was too short, please try again. 202s (process:3264): libfprint-device-DEBUG: 05:38:47.470: Device reported verify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.470: Device reported verify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.470: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.470: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.470: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.471: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.471: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.471: Received command SCAN another-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.471: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.471: Processing command SCAN another-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.471: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.471: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.472: Virtual device scanned print another-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.472: Device reported verify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.472: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.472: Device reported verify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.472: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.472: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.472: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.472: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.472: Got instructions of length 13 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.472: Received command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.473: Processing command SCAN print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.473: Virtual device scanned print print-id 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Device reported verify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Device reported verify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.473: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.473: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.473: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.473: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.473: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.474: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.474: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.474: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.474: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.474: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.474: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.474: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.474: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.474: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.474: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.474: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.475: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.475: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.475: 148314774: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.475: 148314816: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.475: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.475: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.475: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.475: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.475: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.476: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.476: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.476: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.476: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.476: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.476: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.476: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.476: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.477: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Received command RETRY 1 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.477: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.477: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.477: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.478: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.478: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.478: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.478: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.478: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.478: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.478: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.478: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.478: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.478: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.478: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.478: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.478: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.479: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.479: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.479: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.479: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Print for finger FP_FINGER_LEFT_LITTLE enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.479: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.479: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.480: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.480: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.480: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.480: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.480: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.480: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.480: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s ok 202s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.481: 148320769: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.481: 148320805: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-device-DEBUG: 05:38:47.481: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.481: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Received command FINGER 1 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Processing command FINGER 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.482: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Received command FINGER 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Processing command FINGER 0 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Idle cancelling on ongoing operation! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.482: Got cancellation! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.482: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.483: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.483: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.483: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.483: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.483: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.483: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.483: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.484: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.484: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.484: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.484: 148323805: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.484: 148323838: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.484: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.484: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.484: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.484: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.484: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.485: Received command SLEEP 10 202s (process:3264): libfprint-device-DEBUG: 05:38:47.485: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.485: Processing command SLEEP 10 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.485: Sleeping 10ms 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.495: Sleeping completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.495: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.496: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.496: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.496: Received command FINGER 1 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.496: Processing command FINGER 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.496: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.496: Got instructions of length 8 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.496: Received command FINGER 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.496: Processing command FINGER 0 202s (process:3264): libfprint-device-DEBUG: 05:38:47.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Idle cancelling on ongoing operation! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.497: Got cancellation! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.497: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.497: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.497: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.497: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.497: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.498: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.498: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.498: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.498: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.498: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.498: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.498: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.498: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.498: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.498: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.498: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.499: 148338578: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.499: 148338627: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.499: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.499: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.499: Received command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.499: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.499: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.500: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.500: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.500: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.500: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.500: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.501: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.501: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.501: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Print for finger FP_FINGER_RIGHT_THUMB enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.501: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.502: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Received command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.502: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.502: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.502: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.503: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.503: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.503: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Print for finger FP_FINGER_LEFT_THUMB enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.503: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.504: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.504: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.504: Received command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.504: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.504: Trying to identify print 'right-thumb' against a gallery of 2 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.504: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.504: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.504: Received command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.504: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.505: Trying to identify print 'left-thumb' against a gallery of 2 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.505: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.505: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.505: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.505: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.505: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.506: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s Enroll done 202s ok 202s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.506: 148345818: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.506: 148345835: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.506: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.506: Got instructions of length 23 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.506: Received command SCAN not-existing-print 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.506: Processing command SCAN not-existing-print 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.506: Trying to identify print 'not-existing-print' against a gallery of 1 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.506: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.507: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.507: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.507: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.507: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.507: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.508: 148347615: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.508: 148347628: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.508: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.508: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.508: Received command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.508: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.508: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.509: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.509: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.509: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.509: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.510: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.510: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.510: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.510: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.510: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.510: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.510: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.510: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.510: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.511: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.511: Received command SCAN right-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.511: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Print for finger FP_FINGER_RIGHT_THUMB enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.511: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.511: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.511: Received command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.511: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.512: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.512: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.512: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.512: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.512: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.512: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.512: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.512: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.512: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.513: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.513: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.513: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.513: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.514: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.514: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.514: Received command SCAN left-thumb 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.514: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Print for finger FP_FINGER_LEFT_THUMB enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.514: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.514: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.514: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.514: Received command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.515: Processing command SCAN right-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.515: Trying to identify print 'right-thumb' against a gallery of 1 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.515: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.515: Got instructions of length 15 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.515: Received command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.515: Processing command SCAN left-thumb 202s (process:3264): libfprint-device-DEBUG: 05:38:47.515: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:47.516: Trying to identify print 'left-thumb' against a gallery of 1 prints 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.516: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.516: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.516: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.516: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.516: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.517: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.517: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.517: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.517: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.517: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.517: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.517: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.517: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.517: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.517: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s Enroll done 202s Enroll done 202s ok 202s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.517: 148357436: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.518: 148357473: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.518: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.518: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.518: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.518: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.518: Got instructions of length 7 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.518: Received command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.518: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.518: Processing command RETRY 1 202s (process:3264): libfprint-device-DEBUG: 05:38:47.518: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.518: Device reported identify result 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Device reported identify completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.519: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.519: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.519: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.519: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.519: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.519: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.519: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.519: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.519: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.520: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.520: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.520: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.520: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.520: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.520: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.520: 148360201: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.520: 148360238: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.520: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.520: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.521: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s skipped 'Device supports identification' 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.521: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.521: Got instructions of length 5 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.521: Received command CONT 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.521: Processing command CONT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.521: Device reported deletion completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.521: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.521: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.521: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.521: Got instructions of length 16 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.521: Received command SET_KEEP_ALIVE 0 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.521: Keep alive toggled: 0 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.522: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.522: Got instructions of length 19 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.522: Received command SET_ENROLL_STAGES 5 202s (process:3264): libfprint-device-DEBUG: 05:38:47.522: Device reported close completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.522: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.522: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.522: 148362025: ../libfprint/drivers/virtual-device.c:387 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.522: 148362058: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:3264): libfprint-device-DEBUG: 05:38:47.522: Device reported open completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.522: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.522: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.523: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.523: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.523: Received command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.523: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.523: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.523: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.523: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.523: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.523: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.523: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.524: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.524: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.524: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.524: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.524: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.524: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.524: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.524: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.524: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.525: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Sleeping completed 202s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:47.525: Got a new connection! 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Got instructions of length 14 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Received command SCAN testprint 202s (process:3264): libfprint-virtual_device-DEBUG: 05:38:47.525: Processing command SCAN testprint 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported enroll completion 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Print for finger FP_FINGER_RIGHT_THUMB enrolled 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:3264): libfprint-device-DEBUG: 05:38:47.525: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:3264): libfprint-device-DEBUG: 05:38:48.026: Device reported listing completion 203s (process:3264): libfprint-device-DEBUG: 05:38:48.027: Completing action FPI_DEVICE_ACTION_LIST in idle! 203s (process:3264): libfprint-device-DEBUG: 05:38:48.027: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Executing: libfprint-2/virtual-device.test 203s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:48.528: Deleting print testprint for user testuser 203s (process:3264): libfprint-device-DEBUG: 05:38:48.528: Device reported deletion completion 203s (process:3264): libfprint-device-DEBUG: 05:38:48.528: Completing action FPI_DEVICE_ACTION_DELETE in idle! 203s (process:3264): libfprint-device-DEBUG: 05:38:48.528: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-device-DEBUG: 05:38:49.029: Device reported listing completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.029: Completing action FPI_DEVICE_ACTION_LIST in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.029: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.030: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.030: Got instructions of length 5 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.030: Received command CONT 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.030: Processing command CONT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.030: Device reported deletion completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.030: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.030: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.030: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.030: Got instructions of length 16 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.030: Received command SET_KEEP_ALIVE 0 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.031: Keep alive toggled: 0 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.031: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.031: Got instructions of length 19 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.031: Received command SET_ENROLL_STAGES 5 204s (process:3264): libfprint-device-DEBUG: 05:38:49.031: Device reported close completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.031: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.031: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s 204s blub 'testprint' 204s ok 204s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.031: 149871164: ../libfprint/drivers/virtual-device.c:387 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.031: 149871182: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:3264): libfprint-device-DEBUG: 05:38:49.031: Device reported open completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.031: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.031: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.032: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.032: Got instructions of length 14 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.032: Received command SCAN testprint 204s (process:3264): libfprint-device-DEBUG: 05:38:49.032: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.032: Processing command SCAN testprint 204s (process:3264): libfprint-device-DEBUG: 05:38:49.032: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:3264): libfprint-device-DEBUG: 05:38:49.032: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.032: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:3264): libfprint-device-DEBUG: 05:38:49.032: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.033: Sleeping completed 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.033: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.033: Got instructions of length 14 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.033: Received command SCAN testprint 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.033: Processing command SCAN testprint 204s (process:3264): libfprint-device-DEBUG: 05:38:49.033: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.033: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:3264): libfprint-device-DEBUG: 05:38:49.033: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.033: Sleeping completed 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.034: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.034: Got instructions of length 14 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.034: Received command SCAN testprint 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.034: Processing command SCAN testprint 204s (process:3264): libfprint-device-DEBUG: 05:38:49.034: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.034: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:3264): libfprint-device-DEBUG: 05:38:49.034: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.034: Sleeping completed 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.035: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.035: Got instructions of length 14 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.035: Received command SCAN testprint 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.035: Processing command SCAN testprint 204s (process:3264): libfprint-device-DEBUG: 05:38:49.035: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.035: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:3264): libfprint-device-DEBUG: 05:38:49.035: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.035: Sleeping completed 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.035: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.036: Got instructions of length 14 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.036: Received command SCAN testprint 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.036: Processing command SCAN testprint 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Device reported enroll completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Print for finger FP_FINGER_RIGHT_THUMB enrolled 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.036: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.037: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.037: Got instructions of length 16 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.037: Received command REMOVE testprint 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.037: Processing command REMOVE testprint 204s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:49.538: Deleting print testprint for user testuser 204s (process:3264): libfprint-device-DEBUG: 05:38:49.538: Device reported deletion completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.538: Completing action FPI_DEVICE_ACTION_DELETE in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.538: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.538: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.538: Got instructions of length 5 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.538: Received command CONT 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.538: Processing command CONT 204s (process:3264): libfprint-device-DEBUG: 05:38:49.538: Device reported deletion completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.538: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.538: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.539: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.539: Got instructions of length 16 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.539: Received command SET_KEEP_ALIVE 0 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.539: Keep alive toggled: 0 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.539: Got a new connection! 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.539: Got instructions of length 19 204s (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.539: Received command SET_ENROLL_STAGES 5 204s (process:3264): libfprint-device-DEBUG: 05:38:49.539: Device reported close completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.539: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.539: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:49.539: 150379211: ../libfprint/drivers/virtual-device.c:387 204s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:49.539: 150379240: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:3264): libfprint-device-DEBUG: 05:38:49.539: Device reported open completion 204s (process:3264): libfprint-device-DEBUG: 05:38:49.539: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:3264): libfprint-device-DEBUG: 05:38:49.539: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-device-DEBUG: 05:38:50.040: Device reported listing completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.040: Completing action FPI_DEVICE_ACTION_LIST in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.040: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.041: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.041: Got instructions of length 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.041: Received command CONT 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.041: Processing command CONT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.041: Device reported deletion completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.041: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.042: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.042: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.042: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.042: Received command SET_KEEP_ALIVE 0 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.042: Keep alive toggled: 0 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.042: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.042: Got instructions of length 19 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.042: Received command SET_ENROLL_STAGES 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.042: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.042: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.043: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s ok 205s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.043: 150882709: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.043: 150882753: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.043: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.043: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.043: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.043: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.043: Got instructions of length 9 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.043: Received command SLEEP 100 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.044: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.044: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.044: Received command ERROR 4 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.044: Processing command SLEEP 100 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.044: Sleeping 100ms 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.144: Sleeping completed 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.144: Processing command ERROR 4 205s (process:3264): libfprint-device-DEBUG: 05:38:50.144: Device reported listing completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.145: Completing action FPI_DEVICE_ACTION_LIST in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.145: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.145: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.145: Got instructions of length 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.145: Received command CONT 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.145: Processing command CONT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.145: Device reported deletion completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.145: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.145: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.145: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.145: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.145: Received command SET_KEEP_ALIVE 0 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.145: Keep alive toggled: 0 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.146: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.146: Got instructions of length 19 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.146: Received command SET_ENROLL_STAGES 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.146: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.146: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.146: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s ok 205s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.146: 150986031: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.146: 150986053: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.146: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.146: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.146: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.146: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.146: Got instructions of length 9 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.146: Received command INSERT p1 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.147: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Received command SCAN p2 205s (process:3264): libfprint-device-DEBUG: 05:38:50.147: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Processing command INSERT p1 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Processing command SCAN p2 205s (process:3264): libfprint-device-DEBUG: 05:38:50.147: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.147: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.147: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.147: Device reported enroll progress, reported 1 of 5 have been completed 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Sleeping completed 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.147: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Received command SCAN p2 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.147: Processing command SCAN p2 205s (process:3264): libfprint-device-DEBUG: 05:38:50.147: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.148: Device reported enroll progress, reported 2 of 5 have been completed 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.148: Sleeping completed 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.148: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.148: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.148: Received command SCAN p2 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.148: Processing command SCAN p2 205s (process:3264): libfprint-device-DEBUG: 05:38:50.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.148: Device reported enroll progress, reported 3 of 5 have been completed 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.148: Sleeping completed 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.148: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.148: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.149: Received command SCAN p2 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.149: Processing command SCAN p2 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported enroll progress, reported 4 of 5 have been completed 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.149: Sleeping completed 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.149: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.149: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.149: Received command SCAN p2 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.149: Processing command SCAN p2 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported enroll progress, reported 5 of 5 have been completed 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported enroll completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Device reported finger status change: FP_FINGER_STATUS_NONE 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Print for finger FP_FINGER_LEFT_LITTLE enrolled 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.149: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-device-DEBUG: 05:38:50.650: Device reported listing completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.650: Completing action FPI_DEVICE_ACTION_LIST in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.650: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.651: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.651: Got instructions of length 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.651: Received command CONT 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.652: Processing command CONT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.652: Device reported deletion completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.652: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.652: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.652: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.652: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.652: Received command SET_KEEP_ALIVE 0 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.652: Keep alive toggled: 0 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.652: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.652: Got instructions of length 19 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.652: Received command SET_ENROLL_STAGES 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.652: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.653: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.653: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s Enroll done 205s ok 205s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.653: 151492686: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.653: 151492705: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.653: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.653: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.653: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.653: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.653: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.653: Received command IGNORED_COMMAND 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.653: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.653: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.654: Received command ERROR 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.654: Processing command IGNORED_COMMAND 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.654: 151493994: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.654: Processing command ERROR 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s ok 205s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.654: 151494258: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.654: 151494272: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.654: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.655: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: Received command SET_KEEP_ALIVE 1 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: Keep alive toggled: 1 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.655: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: Received command ERROR 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: 151495059: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: Processing command ERROR 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s ok 205s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.655: 151495260: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.655: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.655: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.656: Got instructions of length 19 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.656: Received command SET_ENROLL_STAGES 1 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.656: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.656: Got instructions of length 14 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.656: Received command SCAN testprint 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.656: Processing command SCAN testprint 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Device reported enroll progress, reported 1 of 1 have been completed 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Device reported enroll completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.656: Device reported finger status change: FP_FINGER_STATUS_NONE 205s (process:3264): libfprint-device-DEBUG: 05:38:50.657: Print for finger FP_FINGER_LEFT_LITTLE enrolled 205s (process:3264): libfprint-device-DEBUG: 05:38:50.657: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.657: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.657: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.657: Got instructions of length 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.657: Received command CONT 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.657: Processing command CONT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.657: Device reported deletion completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.657: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.657: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.658: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.658: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.658: Received command SET_KEEP_ALIVE 0 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.658: Keep alive toggled: 0 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.658: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.658: Got instructions of length 19 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.658: Received command SET_ENROLL_STAGES 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.658: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.658: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.658: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s Enroll done 205s ok 205s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.659: 151498646: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.659: 151498676: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.659: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.659: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.659: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.659: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.659: Got instructions of length 23 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.659: Received command SCAN not-existing-print 205s (process:3264): libfprint-device-DEBUG: 05:38:50.659: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.659: Processing command SCAN not-existing-print 205s (process:3264): libfprint-device-DEBUG: 05:38:50.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.660: Virtual device scanned print not-existing-print 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Device reported verify result 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Device reported verify completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Device reported finger status change: FP_FINGER_STATUS_NONE 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.660: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.660: Got instructions of length 5 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.660: Received command CONT 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.660: Processing command CONT 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Device reported deletion completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.660: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.661: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.661: Got instructions of length 16 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.661: Received command SET_KEEP_ALIVE 0 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.661: Keep alive toggled: 0 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.661: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.661: Got instructions of length 19 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.661: Received command SET_ENROLL_STAGES 5 205s (process:3264): libfprint-device-DEBUG: 05:38:50.661: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.661: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.661: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 205s ok 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.662: 151501635: ../libfprint/drivers/virtual-device.c:752 205s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:3264): libfprint-context-DEBUG: 05:38:50.662: Initializing FpContext (libfprint version 1.94.9+tod1) 205s (process:3264): libfprint-tod-DEBUG: 05:38:50.662: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: No driver found for USB device 1D6B:0003 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: No driver found for USB device 0627:0001 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: No driver found for USB device 0627:0001 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: No driver found for USB device 1D6B:0002 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-fsgm5cb0/virtual-device.socket 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: created 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ozyge6tv/virtual-device-storage.socket 205s (process:3264): libfprint-context-DEBUG: 05:38:50.667: created 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Device reported probe completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Device reported probe completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.670: 151509908: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.670: 151509950: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.671: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.671: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.671: Received command UNPLUG 205s (process:3264): libfprint-device-DEBUG: 05:38:50.671: Device reported close completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.671: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.671: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.671: 151511354: ../libfprint/drivers/virtual-device.c:752 205s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:50.671: 151511419: ../libfprint/drivers/virtual-device-storage.c:253 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.671: 151511456: ../libfprint/drivers/virtual-device.c:752 205s ok 205s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:3264): libfprint-context-DEBUG: 05:38:50.672: Initializing FpContext (libfprint version 1.94.9+tod1) 205s (process:3264): libfprint-tod-DEBUG: 05:38:50.672: Impossible to load the shared drivers dir Error opening directory “/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1”: No such file or directory 205s (process:3264): libfprint-context-DEBUG: 05:38:50.676: No driver found for USB device 1D6B:0003 205s (process:3264): libfprint-context-DEBUG: 05:38:50.676: No driver found for USB device 0627:0001 205s (process:3264): libfprint-context-DEBUG: 05:38:50.677: No driver found for USB device 0627:0001 205s (process:3264): libfprint-context-DEBUG: 05:38:50.677: No driver found for USB device 1D6B:0002 205s (process:3264): libfprint-context-DEBUG: 05:38:50.677: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-fsgm5cb0/virtual-device.socket 205s (process:3264): libfprint-context-DEBUG: 05:38:50.677: created 205s (process:3264): libfprint-context-DEBUG: 05:38:50.677: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-ozyge6tv/virtual-device-storage.socket 205s (process:3264): libfprint-context-DEBUG: 05:38:50.677: created 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Device reported probe completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Device reported probe completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Completing action FPI_DEVICE_ACTION_PROBE in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.679: 151519150: ../libfprint/drivers/virtual-device.c:387 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.679: 151519186: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Device reported open completion 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:3264): libfprint-device-DEBUG: 05:38:50.679: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-device-DEBUG: 05:38:50.680: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:3264): libfprint-device-DEBUG: 05:38:50.680: Device reported finger status change: FP_FINGER_STATUS_NEEDED 205s (process:3264): libfprint-virtual_device_connection-DEBUG: 05:38:50.680: Got a new connection! 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.680: Got instructions of length 7 205s (process:3264): libfprint-virtual_device-DEBUG: 05:38:50.680: Received command UNPLUG 205s (process:3264): libfprint-device-DEBUG: 05:38:50.780: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 206s (process:3264): libfprint-device-DEBUG: 05:38:51.181: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 206s (process:3264): libfprint-device-DEBUG: 05:38:51.181: Device reported verify completion 206s (process:3264): libfprint-device-DEBUG: 05:38:51.181: Device reported finger status change: FP_FINGER_STATUS_NONE 206s (process:3264): libfprint-device-DEBUG: 05:38:51.182: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 206s (process:3264): libfprint-device-DEBUG: 05:38:51.182: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 206s (process:3264): libfprint-device-DEBUG: 05:38:51.182: Device reported close completion 206s (process:3264): libfprint-device-DEBUG: 05:38:51.182: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:3264): libfprint-device-DEBUG: 05:38:51.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 206s (process:3264): libfprint-virtual_device-DEBUG: 05:38:51.182: 152022303: ../libfprint/drivers/virtual-device.c:752 206s (process:3264): libfprint-virtual_device_storage-DEBUG: 05:38:51.182: 152022374: ../libfprint/drivers/virtual-device-storage.c:253 206s (process:3264): libfprint-virtual_device-DEBUG: 05:38:51.182: 152022404: ../libfprint/drivers/virtual-device.c:752 206s ok 206s 206s ---------------------------------------------------------------------- 206s Ran 86 tests in 17.690s 206s 206s OK (skipped=1) 206s PASS: libfprint-2/virtual-device.test 206s Running test: libfprint-2/fp-device.test 206s TAP version 14 206s # random seed: R02S4adee81424ab88ea5c0df8a78412ed79 206s 1..17 206s # Start of device tests 206s # Start of async tests 206s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 206s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 206s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DOTD22/virtual_image.socket 206s # libfprint-context-DEBUG: created 206s # libfprint-device-DEBUG: Device reported probe completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.235: 152075350: ../libfprint/drivers/virtual-image.c:216 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:51.236: 152075561: ../libfprint/drivers/virtual-device-listener.c:153 206s # libfprint-image_device-DEBUG: Image device open completed 206s # libfprint-device-DEBUG: Device reported open completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.337: 152176697: ../libfprint/drivers/virtual-image.c:244 206s # libfprint-image_device-DEBUG: Image device close completed 206s # libfprint-device-DEBUG: Device reported close completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 206s ok 1 /device/async/open 206s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 206s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 206s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 206s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ISWL22/virtual_image.socket 206s # libfprint-context-DEBUG: created 206s # libfprint-device-DEBUG: Device reported probe completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.446: 152285779: ../libfprint/drivers/virtual-image.c:216 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:51.446: 152285851: ../libfprint/drivers/virtual-device-listener.c:153 206s # libfprint-image_device-DEBUG: Image device open completed 206s # libfprint-device-DEBUG: Device reported open completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.547: 152386700: ../libfprint/drivers/virtual-image.c:244 206s # libfprint-image_device-DEBUG: Image device close completed 206s # libfprint-device-DEBUG: Device reported close completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 206s ok 2 /device/async/close 206s # End of async tests 206s # Start of sync tests 206s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 206s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 206s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 206s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0WE012/virtual_image.socket 206s # libfprint-context-DEBUG: created 206s # libfprint-device-DEBUG: Device reported probe completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.658: 152497838: ../libfprint/drivers/virtual-image.c:216 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:51.658: 152497983: ../libfprint/drivers/virtual-device-listener.c:153 206s # libfprint-image_device-DEBUG: Image device open completed 206s # libfprint-device-DEBUG: Device reported open completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.759: 152599081: ../libfprint/drivers/virtual-image.c:244 206s # libfprint-image_device-DEBUG: Image device close completed 206s # libfprint-device-DEBUG: Device reported close completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 206s ok 3 /device/sync/open 206s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 206s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 206s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 206s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 206s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-RJO512/virtual_image.socket 206s # libfprint-context-DEBUG: created 206s # libfprint-device-DEBUG: Device reported probe completion 206s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.869: 152708977: ../libfprint/drivers/virtual-image.c:216 206s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:51.869: 152709028: ../libfprint/drivers/virtual-device-listener.c:153 207s # libfprint-image_device-DEBUG: Image device open completed 207s # libfprint-device-DEBUG: Device reported open completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:51.970: 152810004: ../libfprint/drivers/virtual-image.c:244 207s # libfprint-image_device-DEBUG: Image device close completed 207s # libfprint-device-DEBUG: Device reported close completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 207s ok 4 /device/sync/close 207s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 207s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 207s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 207s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-CELB22/virtual_image.socket 207s # libfprint-context-DEBUG: created 207s # libfprint-device-DEBUG: Device reported probe completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.079: 152919327: ../libfprint/drivers/virtual-image.c:216 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:52.079: 152919403: ../libfprint/drivers/virtual-device-listener.c:153 207s # libfprint-image_device-DEBUG: Image device open completed 207s # libfprint-device-DEBUG: Device reported open completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.180: 153020229: ../libfprint/drivers/virtual-image.c:244 207s # libfprint-image_device-DEBUG: Image device close completed 207s # libfprint-device-DEBUG: Device reported close completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 207s ok 5 /device/sync/get_driver 207s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 207s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 207s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 207s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Q16H22/virtual_image.socket 207s # libfprint-context-DEBUG: created 207s # libfprint-device-DEBUG: Device reported probe completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.290: 153129857: ../libfprint/drivers/virtual-image.c:216 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:52.290: 153129927: ../libfprint/drivers/virtual-device-listener.c:153 207s # libfprint-image_device-DEBUG: Image device open completed 207s # libfprint-device-DEBUG: Device reported open completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.391: 153230853: ../libfprint/drivers/virtual-image.c:244 207s # libfprint-image_device-DEBUG: Image device close completed 207s # libfprint-device-DEBUG: Device reported close completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 207s ok 6 /device/sync/get_device_id 207s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 207s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 207s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 207s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Y5KK22/virtual_image.socket 207s # libfprint-context-DEBUG: created 207s # libfprint-device-DEBUG: Device reported probe completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.497: 153336578: ../libfprint/drivers/virtual-image.c:216 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:52.497: 153336621: ../libfprint/drivers/virtual-device-listener.c:153 207s # libfprint-image_device-DEBUG: Image device open completed 207s # libfprint-device-DEBUG: Device reported open completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.597: 153437286: ../libfprint/drivers/virtual-image.c:244 207s # libfprint-image_device-DEBUG: Image device close completed 207s # libfprint-device-DEBUG: Device reported close completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 207s ok 7 /device/sync/get_name 207s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 207s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 207s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 207s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-76Z412/virtual_image.socket 207s # libfprint-context-DEBUG: created 207s # libfprint-device-DEBUG: Device reported probe completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.707: 153546800: ../libfprint/drivers/virtual-image.c:216 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:52.707: 153546852: ../libfprint/drivers/virtual-device-listener.c:153 207s # libfprint-image_device-DEBUG: Image device open completed 207s # libfprint-device-DEBUG: Device reported open completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.808: 153647739: ../libfprint/drivers/virtual-image.c:244 207s # libfprint-image_device-DEBUG: Image device close completed 207s # libfprint-device-DEBUG: Device reported close completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 207s ok 8 /device/sync/get_scan_type 207s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 207s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 207s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 207s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 207s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ED0512/virtual_image.socket 207s # libfprint-context-DEBUG: created 207s # libfprint-device-DEBUG: Device reported probe completion 207s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 207s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:52.918: 153757666: ../libfprint/drivers/virtual-image.c:216 207s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:52.918: 153757735: ../libfprint/drivers/virtual-device-listener.c:153 208s # libfprint-image_device-DEBUG: Image device open completed 208s # libfprint-device-DEBUG: Device reported open completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.019: 153858862: ../libfprint/drivers/virtual-image.c:244 208s # libfprint-image_device-DEBUG: Image device close completed 208s # libfprint-device-DEBUG: Device reported close completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 208s ok 9 /device/sync/get_finger_status 208s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 208s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 208s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 208s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5VWB22/virtual_image.socket 208s # libfprint-context-DEBUG: created 208s # libfprint-device-DEBUG: Device reported probe completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.127: 153966490: ../libfprint/drivers/virtual-image.c:216 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:53.127: 153966645: ../libfprint/drivers/virtual-device-listener.c:153 208s Executing: libfprint-2/fp-device.test 208s # libfprint-image_device-DEBUG: Image device open completed 208s # libfprint-device-DEBUG: Device reported open completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.227: 154067416: ../libfprint/drivers/virtual-image.c:244 208s # libfprint-image_device-DEBUG: Image device close completed 208s # libfprint-device-DEBUG: Device reported close completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 208s ok 10 /device/sync/get_nr_enroll_stages 208s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 208s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 208s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 208s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-UK3G22/virtual_image.socket 208s # libfprint-context-DEBUG: created 208s # libfprint-device-DEBUG: Device reported probe completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.334: 154173915: ../libfprint/drivers/virtual-image.c:216 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:53.334: 154173949: ../libfprint/drivers/virtual-device-listener.c:153 208s # libfprint-image_device-DEBUG: Image device open completed 208s # libfprint-device-DEBUG: Device reported open completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.435: 154275321: ../libfprint/drivers/virtual-image.c:244 208s # libfprint-image_device-DEBUG: Image device close completed 208s # libfprint-device-DEBUG: Device reported close completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 208s ok 11 /device/sync/supports_identify 208s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 208s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 208s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 208s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-8AK112/virtual_image.socket 208s # libfprint-context-DEBUG: created 208s # libfprint-device-DEBUG: Device reported probe completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.546: 154385488: ../libfprint/drivers/virtual-image.c:216 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:53.546: 154385564: ../libfprint/drivers/virtual-device-listener.c:153 208s # libfprint-image_device-DEBUG: Image device open completed 208s # libfprint-device-DEBUG: Device reported open completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.646: 154486284: ../libfprint/drivers/virtual-image.c:244 208s # libfprint-image_device-DEBUG: Image device close completed 208s # libfprint-device-DEBUG: Device reported close completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 208s ok 12 /device/sync/supports_capture 208s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 208s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 208s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 208s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-53J212/virtual_image.socket 208s # libfprint-context-DEBUG: created 208s # libfprint-device-DEBUG: Device reported probe completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.753: 154592886: ../libfprint/drivers/virtual-image.c:216 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:53.753: 154592961: ../libfprint/drivers/virtual-device-listener.c:153 208s # libfprint-image_device-DEBUG: Image device open completed 208s # libfprint-device-DEBUG: Device reported open completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.854: 154693875: ../libfprint/drivers/virtual-image.c:244 208s # libfprint-image_device-DEBUG: Image device close completed 208s # libfprint-device-DEBUG: Device reported close completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 208s ok 13 /device/sync/has_storage 208s # Start of open tests 208s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 208s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 208s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 208s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 208s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-JGVA22/virtual_image.socket 208s # libfprint-context-DEBUG: created 208s # libfprint-device-DEBUG: Device reported probe completion 208s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 208s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:53.964: 154803984: ../libfprint/drivers/virtual-image.c:216 208s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:53.964: 154804255: ../libfprint/drivers/virtual-device-listener.c:153 209s # libfprint-image_device-DEBUG: Image device open completed 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.066: 154905859: ../libfprint/drivers/virtual-image.c:244 209s # libfprint-image_device-DEBUG: Image device close completed 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 209s ok 14 /device/sync/open/notify 209s # End of open tests 209s # Start of close tests 209s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FTFG22/virtual_image.socket 209s # libfprint-context-DEBUG: created 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.173: 155013434: ../libfprint/drivers/virtual-image.c:216 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:54.173: 155013464: ../libfprint/drivers/virtual-device-listener.c:153 209s # libfprint-image_device-DEBUG: Image device open completed 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.274: 155114434: ../libfprint/drivers/virtual-image.c:244 209s # libfprint-image_device-DEBUG: Image device close completed 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 209s ok 15 /device/sync/close/notify 209s # End of close tests 209s # Start of identify tests 209s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0BRH22/virtual_image.socket 209s # libfprint-context-DEBUG: created 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.382: 155222094: ../libfprint/drivers/virtual-image.c:216 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:54.382: 155222141: ../libfprint/drivers/virtual-device-listener.c:153 209s # libfprint-image_device-DEBUG: Image device open completed 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.483: 155322917: ../libfprint/drivers/virtual-image.c:244 209s # libfprint-image_device-DEBUG: Image device close completed 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 209s ok 16 /device/sync/identify/cancelled 209s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/powerpc64le-linux-gnu/libfprint-2/tod-1?: No such file or directory 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-8MV112/virtual_image.socket 209s # libfprint-context-DEBUG: created 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.593: 155433013: ../libfprint/drivers/virtual-image.c:216 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_device_connection-DEBUG: 05:38:54.593: 155433090: ../libfprint/drivers/virtual-device-listener.c:153 209s # libfprint-image_device-DEBUG: Image device open completed 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:3280): libfprint-virtual_image-DEBUG: 05:38:54.694: 155534075: ../libfprint/drivers/virtual-image.c:244 209s # libfprint-image_device-DEBUG: Image device close completed 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 209s ok 17 /device/sync/identify/null-prints 209s # End of identify tests 209s # End of sync tests 209s # End of device tests 209s PASS: libfprint-2/fp-device.test 209s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 209s TAP version 14 209s # random seed: R02S65edde78a7c9f112ce3113572a7e66fa 209s 1..14 209s # Start of device tests 209s # Start of async tests 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 1 /device/async/open 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 2 /device/async/close 209s # End of async tests 209s # Start of sync tests 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 3 /device/sync/open 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 4 /device/sync/close 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 5 /device/sync/get_driver 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 6 /device/sync/get_device_id 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 7 /device/sync/get_name 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 8 /device/sync/get_scan_type 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 9 /device/sync/get_nr_enroll_stages 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 10 /device/sync/supports_identify 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 11 /device/sync/supports_capture 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 12 /device/sync/has_storage 209s # Start of open tests 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 13 /device/sync/open/notify 209s # End of open tests 209s # Start of close tests 209s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 209s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 209s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x775edd693590, GType is 15672362431008 209s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 209s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 209s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 209s # libfprint-context-DEBUG: created 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 209s # 209s # libfprint-device-DEBUG: Device reported probe completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 209s # 209s # libfprint-device-DEBUG: Device reported open completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 209s # 209s # libfprint-device-DEBUG: Device reported close completion 209s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 14 /device/sync/close/notify 209s # End of close tests 209s # End of sync tests 209s # End of device tests 209s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 209s SUMMARY: total=36; passed=36; skipped=0; failed=0; user=32.2s; system=10.0s; maxrss=70016 210s autopkgtest [05:38:55]: test installed-tests: -----------------------] 211s installed-tests PASS 211s autopkgtest [05:38:56]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 212s autopkgtest [05:38:57]: @@@@@@@@@@@@@@@@@@@@ summary 212s installed-tests PASS 216s nova [W] Using flock in prodstack6-ppc64el 216s Creating nova instance adt-plucky-ppc64el-libfprint-20250222-053524-juju-7f2275-prod-proposed-migration-environment-15-93f617db-f8bc-41ee-b30b-4f1ac4820118 from image adt/ubuntu-plucky-ppc64el-server-20250222.img (UUID fe93544b-49e9-47e0-b80a-745acc8cd85b)... 216s nova [W] Timed out waiting for 5b4ae397-32e9-4cc2-b01b-8fd295247d73 to get deleted.